> For the complete documentation index, see [llms.txt](https://deploykey.gitbook.io/deploykey-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deploykey.gitbook.io/deploykey-docs/windows-11-keys/key-type-comparison.md).

# Key Type Comparison

#### Windows 11 Retail

{% hint style="success" %}
This key is for any customer. This is the same type of key you would receive if you were buying from Microsoft, BestBuy, Microcenter, etc.
{% endhint %}

#### Windows 11 OEM

{% hint style="info" %}
This key is for system builders only.
{% endhint %}

#### Windows 11 Volume

{% hint style="danger" %}
***We does not sell this type of key and we do not intend on selling it.*** Volume keys are for large businesses that have several computers. Unlike Retail and OEM, one key will activate several different computers. These keys can be deactivated by the businesses or Microsoft at any time. We highly advise avoiding any key selling service that offers volume keys.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://deploykey.gitbook.io/deploykey-docs/windows-11-keys/key-type-comparison.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.