With Extend, your cost depends on what you run (e.g. Parse, Classify, Split, Extract, Edit Runs, Edit Schema Generation), how you run them (e.g. Performance vs. Light modes), and your plan’s credit rate (Pay as you go, Scale, or Enterprise).
Instead of fixed fees, you only pay for the specific processors you need, at the level of performance you require.
🤖 ** Parse runs automatically when Extract, Split, or Classify processors are used.
💡 Edit pricing:
The following optional features add surcharges on top of the base credit rates when enabled.
The Review Agent automatically flags results for quality assurance and adds a more reliable confidence score. It is available for both extraction and classification processors.
When enabled, agentic correction features use a vision language model (VLM) to review and correct OCR results during parsing.
Note: When enabled for a document, agentic corrections only applies/charges for pages where the agentic correction was triggered (e.g. low confidence text blocks, tables, etc.).
Priority parsing guarantees faster p90+ parse results on the light parsing pipeline. Reach out to the Extend team if you need to enable this for your account.
Large Array Max Context does multiple passes through the entire document to maximize accuracy for complex array extraction, doubling the base extraction credit cost.
Advanced Excel parsing uses LLM-based layout detection for better table separation and header recognition in complex spreadsheets. Billed per cell rather than per page. Does not include empty cells.
💡 Formula: base credits per page × your plan's per-credit rate = $/page (plus any applicable surcharges)
Processing a 10-page document through a Splitting & Extraction workflow on Performance mode, would consume 70 credits in total, itemized as follows:
If the same extraction run also has the Review Agent enabled, it would add 10 credits (10 pages * 1 credit), for a total of 80 credits.
If the parsing step used the race pipeline strategy and had agentic text correction trigger on 5 pages and agentic table correction trigger on 3 pages, parsing would cost 48 credits (10 * 2 * 2 for race + 5 * 1 for text correction + 3 * 1 for table correction) instead of 20.


You can categorize your workflow, processor, and parser runs for better billing and usage tracking by including usage tags in your run metadata. This allows you to filter and visualize credit usage in the dashboard based on different dimensions like environment, team, or customer.
Include usage tags in your run metadata using the extend:usage_tags key with an array of string values:
Allowed characters: Only alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and underscores (_)
Removed characters: All special characters and symbols are stripped out, including:
The credits dashboard provides multiple filters to help you analyze your usage:
You can combine multiple filters to create detailed views of your usage patterns.
Looking for ways to improve workflow efficiency, or curious if Performance or Light mode is right for you? Book a consultation with the team here!