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

# Per-Page Billing Breakdown

> Understand exactly which billing features were applied to each page of your document

Every Parse response includes a `page_billing_breakdown` field inside `usage` that tells you exactly which billable features were applied to each page. This gives you granular visibility into your credit consumption.

## Response Format

The `page_billing_breakdown` is a map from **1-indexed page number** (as a string) to an array of billing feature tags applied to that page:

```json theme={null}
{
  "usage": {
    "num_pages": 5,
    "credits": 15.0,
    "credit_breakdown": {
      "page": 5.0,
      "agentic": 5.0,
      "complex": 3.0
    },
    "page_billing_breakdown": {
      "1": ["agentic", "page"],
      "2": ["agentic", "complex", "page"],
      "3": ["agentic", "chart_agent", "page"],
      "4": ["agentic", "chart_agent", "complex", "page"],
      "5": ["agentic", "page"]
    }
  }
}
```

## Billing Features

Each page can have one or more of the following feature tags:

| Feature                      | Description                                      | When Applied                                                          |
| ---------------------------- | ------------------------------------------------ | --------------------------------------------------------------------- |
| `page`                       | Standard page processing                         | Every PDF/image page                                                  |
| `html_page`                  | HTML document page                               | HTML and text file pages                                              |
| `docx_native_page`           | Native DOCX page                                 | Word documents processed natively                                     |
| `agentic`                    | Agentic extraction enabled                       | When any agentic mode is configured (text, tables, figures)           |
| `complex`                    | Complex page processing                          | Pages with complex tables, key-value regions, or figure summarization |
| `chart_agent`                | Advanced chart extraction                        | Pages where the chart agent ran                                       |
| `billable_spreadsheet_pages` | Spreadsheet page billing derived from cell count | Spreadsheet pages (XLSX, CSV, etc.)                                   |

### Feature Collapsing

Several internal work types are collapsed into simplified categories for clarity:

* **`complex`** combines: `figure_summary`, `table_summary`, and `key_value` work types. If a page has multiple complex operations (e.g., both a complex table and a figure summary), it still appears as a single `complex` tag.
* **`page`**, **`html_page`**, and **`docx_native_page`** are mutually exclusive base page types depending on the document format.
* **`billable_spreadsheet_pages`** is the current spreadsheet billing tag. During rollout compatibility, older persisted responses may still show `spreadsheet_cells`.

## Related

<CardGroup cols={2}>
  <Card title="Credit Usage" icon="coins" href="/reference/credit-usage">
    Full credit rates for all endpoints.
  </Card>

  <Card title="Parse Response Format" icon="file-lines" href="/parse/response-format">
    Complete parse response structure.
  </Card>
</CardGroup>