> For the complete documentation index, see [llms.txt](https://docs.aimlapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aimlapi.com/api-references/vision-models.md).

# Vision Models

Overview of the capabilities of AIML API vision models.

## Overview

Our API enables you to use machine learning models for tasks that require visual capabilities. These models are referred to as *vision models*. Within our API, we offer two categories of vision models: **OCR** and **OFR**.

### OCR: Optical Character Recognition

With OCR technology, you can analyze any document and extract text as well as other characters and symbols. This allows you to detect:

* Text
* Paragraph blocks
* Handwriting
* Text inside PDF/TIFF files

{% content-ref url="/pages/CODp2ueb2n1V1CVefRsT" %}
[OCR: Optical Character Recognition](/api-references/vision-models/ocr-optical-character-recognition.md)
{% endcontent-ref %}

### OFR: Optical Feature Recognition

In contrast to OCR, OFR allows you to analyze not just documents but also images. You can filter exactly what you want to find in the image by the features they include:

* Crop hints
* Faces
* Image properties
* Labels
* Landmarks
* Logos
* Multiple objects
* Explicit content
* Web entities and pages
* And many more

{% content-ref url="/pages/h0B352jf7zT5hlI2C7vV" %}
[OFR: Optical Feature Recognition](/api-references/vision-models/ofr-optical-feature-recognition.md)
{% endcontent-ref %}


---

# 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.aimlapi.com/api-references/vision-models.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.