> 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/models/pricing.md).

# Credit Cost

Information on credit consumption for processing documents using a given model.

Each file successfully processed by a model will consume credits based on the number of pages contained in the file.

By default, Extraction models consume 1 credit per page.

Files that are sent but not processed (i.e. job status "Failed", or HTTP 400) do not consume credits.

The model's "Credit Cost" page shows the exact amount of credits consumed per page processed.

For files having more than one page, such as PDF or TIFF, this is every page of the file.\
Single image files count as one page.

For example, using an Extraction model with no [extra features](/extraction-models/optional-features.md) activated:

* Single page text PDF file ⇒ 1 credit
* 5 page text and image PDF file ⇒ 5 credits
* A JPEG file ⇒ 1 credit

{% hint style="info" %}
Ratio of 1 credit per page is the **default** value.

Depending on the model type and options activated, credits consumed per page may be lower or higher.

**Always check the model's Credit Cost page for the exact amount of credits consumed.**
{% 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 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/models/pricing.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.