> 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/extraction-models/optional-features/raw-text-full-ocr.md).

# Raw Text (Full OCR)

Add the full text content of your documents to the API response.

## Overview

By activating this feature, the full text content of the document will be extracted using OCR (Optical Character Recognition) technology.

The resulting content will be included in the API response.

In the response, each page will have its text content filled.

## Use Cases

Having access to the raw text can be particularly useful when:

* needing to save a copy of the text for your records
* perform searches within the text

## Activate Raw Text

### Activate Raw Text via API Calls

If you need finer-grained control over when the feature is used, you can activate or deactivate it when making API calls.

This allows dynamically setting the activation state using your internal business or domain logic.

Check the [Client Configuration](/integrations/client-libraries-sdk/configure-the-client.md#optional-features-configuration) section if using our [Client Libraries / SDKs](/integrations/client-libraries-sdk.md).

## Use the Raw Text Result

We highly recommend using our [Client Libraries / SDKs](/integrations/client-libraries-sdk.md), as they include various functions for ease of processing.

Specifically for handling the raw text, take a look at the [Response Processing](/integrations/client-libraries-sdk/process-the-response.md#raw-text) section.

Otherwise, take a look at the [Manual Integration](/integrations/api-reference.md#get-v2-inferences-inference_id) section.


---

# 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/extraction-models/optional-features/raw-text-full-ocr.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.