Skip to main content
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: 
{
  "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:
FeatureDescriptionWhen Applied
pageStandard page processingEvery PDF/image page
html_pageHTML document pageHTML and text file pages
docx_native_pageNative DOCX pageWord documents processed natively
agenticAgentic extraction enabledWhen any agentic mode is configured (text, tables, figures)
complexComplex page processingPages with complex tables, key-value regions, or figure summarization
chart_agentAdvanced chart extractionPages where the chart agent ran
spreadsheet_cellsSpreadsheet cell processingSpreadsheet 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.

Credit Usage

Full credit rates for all endpoints.

Parse Response Format

Complete parse response structure.