> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/v1/platform-ui-tour/api-hub.md).

# Document Catalog

When you log into Mindee, you will land on the APIs page. This page is organized into four main sections:

* My APIs,
* Document Catalog,
* Utilities,
* docTI.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-a896170671d687772d2ca7066db90c51f57f6dc3%2Fe3e54d82180f9af9307a5f0b37b32eb135aed3388639c069cfc69f16b5b2136e-image.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

In the **My APIs** section, you will find a list of APIs that you are currently using. This includes any API that you have made at least one call to or subscribed to, as well as any APIs you have generated using docTI.

The **Document Catalog** section displays all the Off-the-Shelf (OTS) APIs that are available. These are ready-to-test and use APIs, and you will find a complete list of all our OTS APIs in this section.

The **Utilities** section includes various utility APIs. These utility APIs encompass the

* Barcode Reader,
* Multi Receipt Detector,
* Cropper,
* Invoice Splitter.

The **docTI** section is where you can create custom extraction and classification endpoints. docTI allows you to process documents without any training required. Once you finalize these endpoints, they will be displayed in the My APIs tab. If you need guidance, follow [this tutorial](/v1/docti/set-up-your-custom-api.md) to help you through the process of creating your own API.

## API Filtering by Location

To make it easier to find the most relevant off-the-shelf APIs, you can filter them by location on the APIs page. This feature simplifies the process of locating APIs that are suited to your specific needs. However, all available off-the-shelf APIs are accessible regardless of your location.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-f6bf67d089cf15f38898a67163b7d2f2bb151192%2F819244a9147ca383200aa0d87270bdfa76348aef373d308f03073a36103bd3f5-image.png?alt=media" alt=""><figcaption></figcaption></figure>

You can filter your off-the-shelf APIs in the APIs store by location; this makes it easier to find the APIs you wish to use. However, regardless of your location, you will be able have access to all available off-the-shelf APIs.

Some of the APIs listed are relevant only to a certain location; for example, the French ID card API won't be that relevant to someone in the United States unless there is a specific need for it.


---

# 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.mindee.com/v1/platform-ui-tour/api-hub.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.
