> For the complete documentation index, see [llms.txt](https://docs.cow.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cow.tech/troubleshooting/supported-device-types.md).

# Supported Device Types

COW supports automatic warranty management on a best effort basis for the following device manufacturers:

* Apple (pre-2022 models)
* Dell
* HP
* Lenovo
* Microsoft
* Toshiba, including devices listed as dynabook

Devices from other manufacturers, such as ASUS, Acer and Samsung, are still listed on the [Devices](/using-cow/navigation/devices.md) page with their manufacturer, but COW does not look up their warranties.

## Detecting the manufacturer from a serial number

When no manufacturer is given, COW guesses it from the length of the serial number and marks the guess with `(Autodetect)`:

| Serial length       | Detected manufacturer |
| ------------------- | --------------------- |
| 7 characters        | Dell                  |
| 8 characters        | Lenovo                |
| 9 characters        | Toshiba               |
| 10 characters       | HP                    |
| 12 or 14 characters | Microsoft             |

A serial of any other length is left as `Unknown`. Apple serials are not detected this way.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cow.tech/troubleshooting/supported-device-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.