> For the complete documentation index, see [llms.txt](https://docs.miniai.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miniai.live/product/id-document-recognition-sdk/supported-id-document-types.md).

# Supported ID Document Types

Our database contains more than 14,000 types of documents from 251 countries and territories of the world. Here are the most common ones.

Border Crossing Card, Business Travel Card, Citizenship Card, Crew member certificate, Diplomatic Id Card, Driving License, ePassport, Health Insurance Card, ID Card, Immigration Card, Insurance Board Card, Laissez-Passer, Lawyer Card, Marine License, Medicare Card, Passport, Personal Card, Police Card, Proof of Age Card, Refugee Card, Registration Certificate, Residence permit, Social Security Card, Visa, Voter Card, Work Permit, and others.

You can find the list of supported ID documents in the [Documents Database (PDF file)](https://drive.google.com/file/d/1TrNjyMoP-RVagnsQc6FqPXSZjFcuYRl2/view?usp=sharing).

{% hint style="info" %}
Note: Didn't find your identity document in the list?

You can contact us to request add your documents in our database. Our team will support to add your specific documents in the list.
{% 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://docs.miniai.live/product/id-document-recognition-sdk/supported-id-document-types.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.