> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anyformat.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage & Billing

> How anyformat measures usage and how it shows up in billing.

Usage is based on **how much document content is processed**, not on:

* How complex your schema is
* How many fields you define

The main driver is **pages**. Each time anyformat processes a document, it counts the pages in that document. So:

* A 1-page invoice counts as 1 page.
* A 50-page report counts as 50 pages.
* Processing 100 single-page invoices counts as 100 pages.

Adding more fields to your schema, or more steps to your workflow, does **not** increase usage — only the amount of document content does. Documents that fail with an error are not counted.

***

## Why usage works this way

This model:

* Scales predictably
* Reflects real processing cost
* Encourages starting simple

You don't need to optimize usage early. Understanding the basics is enough until you scale.

***

## Pricing

Usage is billed in **credits** — a fixed number per operator, the same on every plan. See [How credits work](/concepts/how-credits-work) for the full per-operator breakdown, a worked example, and what a credit is worth on your plan.

For custom or enterprise pricing, contact us at [info@anyformat.ai](mailto:info@anyformat.ai).

***

## When to come back to this

You'll want to re-read this when:

* You process large volumes
* Costs start to matter
* Documents behave unexpectedly
* You're debugging processing issues

***

## What's next?

<CardGroup cols={2}>
  <Card title="How credits work" icon="coins" href="/concepts/how-credits-work">
    Per-operator credit costs and a worked example
  </Card>

  <Card title="Schemas" icon="database" href="/concepts/schemas">
    Define what data you want
  </Card>

  <Card title="Workflows" icon="arrows-rotate" href="/concepts/workflows">
    Run your schema repeatedly at scale
  </Card>
</CardGroup>