> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/supported-documents.md).

# Supported Documents

Identity documents and regions supported by 1Kosmos for document scanning and verification.

***

### Overview

1Kosmos can be used to scan both Identity documents (ID, DL, Passports, and so on) and Medical documents. Each document type has been issued in multiple versions throughout the years, and document design is usually significantly changed across versions. Some document changes that we have observed are: change in orientation (horizontal vs vertical), addition or replacement of the script of the document (Latin, Cyrillic, Arabic), security feature changes, and other similar updates. Key document features on supported documents are noted below (for example, document orientation and script), as well as supported document sides (front, back, bio-data page, and so on).

The table below lists the supported documents for each country, along with the corresponding region.

Here is the full list

{% embed url="<https://www.1kosmos.com/platform/resources/supported-documents>" %}

{% hint style="info" %}
Other than the documents listed here, 1Kosmos Recognizers also scan the **Machine Readable Zone (MRZ)** on standard (ISO/IEC 7501 compliant) **Machine Readable Travel Documents (MRTD)**. This includes **passports, visas,** and other identification documents.&#x20;
{% 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 by asking a question.

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

```
GET https://docs.1kosmos.com/identity-verification/supported-documents.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.
