> ## 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.
# Pricing Migration Guide
> How Reducto's move from credit-based billing to per-product pricing affects you
## TL;DR
* Effective September 1, 2026, Reducto is introducing a new pricing structure. See [Usage and Pricing](/reference/credit-usage) for the full list rates.
* No existing customer will pay more in their current term as a result of these changes. Your pricing will either stay the same or decrease.
* For many customers, we're decreasing the cost across Extract, Deep Extract, and Split.
* Contracted customers do not need to take any action. Your current credit-based pricing and any applicable discounts remain in place until renewal.
* For existing pay-as-you-go customers, the new pricing takes effect on September 1, 2026. No action is required to take advantage of these pricing improvements.
## Plan migration timeline
| When | What changes |
| :---------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| September 1, 2026 | Per-product pricing becomes the default for all new customers. Existing pay-as-you-go customers will automatically get the new list credit rates (see below). All credits will transfer over. Contracted customers will not see their rates change, aside from built-in savings (e.g., parsing being included in Extract). |
| October 1, 2026 | New Standard tier pay-as-you-go customers move automatically to per-product rate cards. |
| At renewal | Contracted customers move only when they sign a new contract or rate card. Until then, existing pricing remains in place. |
## Key pricing changes
| Product | Old pricing | New pricing (effective 9/1/2026) |
| :--------------- | :-------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------- |
| \[New] r-1 Parse | N/A | \$10 / 1,000 pages |
| Extract | \$20 / 1,000 pages. Parse billed separately, an additional \$10 / 1,000 pages up to \$40 / 1,000 pages. | \$20 / 1,000 pages, including parsing. Dense extractions (over 100 fields/page) may incur a per-field surcharge. |
| Deep Extract | \$40 / 1,000 pages plus \$1 / 1,000 pages per field extracted. Minimum of 30 credits per document. Parse billed separately. | \$40 / 1,000 pages, including parsing. Dense extractions (over 100 fields/page) may incur a per-field surcharge. |
| Split | \$20 / 1,000 pages. Parse billed separately. \$40 / 1,000 pages for Deep Split. Parse billed separately. | \$20 / 1,000 pages, including parsing. \$40 / 1,000 pages for Deep Split, including parsing. |
For the rates that applied before this change, see [Legacy Credit Usage](/reference/legacy-credit-usage).
## Which pricing model am I on?
Your response tells you which model you are on. Per-product accounts receive a `usage_breakdown` object, and their credit fields are `null`. Credit-based accounts receive a numeric `credits` value and no `usage_breakdown` key. Test for the presence of the key, not for `credits` being `null`.
Your plan tells you when this changes:
* Accounts created after September 1, 2026 are on the new rate cards.
* Existing pay-as-you-go accounts move to per-product rate cards on October 1, 2026. The new list credit rates apply from September 1, 2026.
* Contracted accounts change at their next renewal.
## What your API responses look like
API responses use one of two usage shapes. Accounts on credit-based rate cards receive a numeric `credits` value. Parse, split, and edit responses also include `credit_breakdown` and `page_billing_breakdown`. Accounts on per-product pricing receive raw quantities in `usage_breakdown` and no credit total. Their credit fields are `null`.
### Credit-based accounts
Credit-based accounts receive the response shape they see today. The `usage_breakdown` key is absent from the JSON.
This example shows a parse response.
```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"]
}
}
}
```
### Per-product accounts
Per-product accounts receive raw quantities in `usage_breakdown`. The credit fields are `null`. The fields depend on the endpoint.
This example shows a parse response.
```json theme={null}
{
"usage": {
"num_pages": 5,
"credits": null,
"credit_breakdown": null,
"page_billing_breakdown": null,
"usage_breakdown": {
"parse_model": "R-1",
"tier": "Default",
"parse_pages": 5,
"parse_native_pages": 0,
"legacy_parse_credits": 0.0,
"ocr_pages": 2,
"charts": 1,
"prompted_blocks": 0
}
}
}
```
## What existing customers need to do
* Accounts moved to per-product pricing now receive `usage_breakdown` instead of the credit fields. It reports product-specific quantities. See [What your API responses look like](#what-your-api-responses-look-like).
* Existing pay-as-you-go customers will have their changes take place on September 1, 2026.
* Contracted customers will keep their current credit-based pricing, and any applicable discounts remain in place. Contact your CSM or support if you have any questions about how this change affects your individual plan.
## FAQ
If you signed up for Reducto after September 1, 2026, your account will automatically use the new pricing.
Yes. New customers will still have 15,000 credits to use.
All pre-paid credits will carry over with no action required.
While your account stays on credit-based pricing, `usage.credits` keeps its current value. Once your account moves to a per-product rate card, `usage.credits` is `null`, and you should read quantities from `usage_breakdown` instead. See [What your API responses look like](#what-your-api-responses-look-like).
All Standard pay-as-you-go customers will automatically move to the new pricing on September 1, 2026. All Growth and Enterprise customers retain their contracted pricing structure until renewal.
## Related
Current list pricing across all Reducto products.
Credit rates that applied before September 1, 2026.
Details about billing features applied to each page.