> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/document-ai/api-reference/utility.md).

# Doc AI Utility

Discover what the platform can accept before you send it anything.

Two lookup endpoints answer the questions every integration asks first: *which document types can I name*, and *which file formats will you take*. Both are worth calling at build time rather than hardcoding, because the document-type registry grows without a release — new types are added as configuration.

### Get supported file types for all document types.

`GET /document/supported-file-types`

Requires the `X-Api-Key` header.

**Responses**

| Status | Description                                                             | Schema                       |
| ------ | ----------------------------------------------------------------------- | ---------------------------- |
| `200`  | OK                                                                      | `SupportedFileTypesResponse` |
| `400`  | Bad Request                                                             | `ValidationError`            |
| `401`  | Authentication required — the `X-Api-Key` header is missing or invalid. |                              |

**Example**

```bash
curl -X GET "https://<api-host>/document/supported-file-types" \
  -H "X-Api-Key: $DOCAI_API_KEY"
```

### List all supported document types from YAML configs.

`GET /listSupportedDocuments`

No authentication required.

**Responses**

| Status | Description | Schema                           |
| ------ | ----------- | -------------------------------- |
| `200`  | OK          | `ListSupportedDocumentsResponse` |
| `400`  | Bad Request | `ValidationError`                |

**Example**

```bash
curl -X GET "https://<api-host>/listSupportedDocuments"
```

### Related pages

* [Document Types](https://docs.uptiq.ai/document-ai/guides/document-types.md) — the same registry, categorised and annotated.


---

# 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.uptiq.ai/document-ai/api-reference/utility.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.
