MiniMax M3.1 Flash API cost estimates for structured extraction
Estimate MiniMax M3.1 Flash extraction costs using explicit token assumptions, JSON Schema validation, and comparable published rates.
Summary · TL;DR
An illustrative workload of 150,000 structured-extraction requests per month costs $103.50 at the cited official rates or $29.601 at the published OneMux rates, before retries, caching, and other charges.
Key Takeaways
- At 3,000 input and 400 output tokens, the illustrative token cost is $0.00069 per request at the cited official rates and $0.00019734 at OneMux rates.
- Validate every extraction locally against a JSON Schema; syntactic validity alone does not establish that extracted values are correct.
- Cache savings require eligible cache reads, while retries consume additional tokens and can offset savings.
- Rates are a dated snapshot, not a guarantee of current prices or workload performance.
On this page (9)
The estimate in brief
For an illustrative structured-extraction workload of 150,000 requests per month, with 3,000 input tokens and 400 output tokens per request, MiniMax M3.1 Flash token charges come to $103.50 at the cited official rates or $29.601 at the published OneMux rates. That is before retries, cache reads, taxes, gateway charges, or other applicable costs.
OneMux is the publisher and a product discussed in this cost guide. These are estimates, not measured invoices or a quality comparison. Use your own token counts and verify current terms before budgeting.
Rates and assumptions
The Future AGI model page lists the Fireworks AI model's input and output rates and says its pricing was verified on October 22, 2026. The OneMux catalogue snapshot was captured on November 12, 2026. The snapshot date records the catalogue values; it does not establish when the model was released or whether the prices remain current.
All rates below are USD per 1 million tokens. The published ratio is OneMux's price divided by the corresponding official price, not a percentage discount.
| Token category | Official rate | OneMux rate | Published price ratio |
|---|---|---|---|
| Input | $0.15 | $0.0429 | 0.286 |
| Output | $0.60 | $0.1716 | 0.286 |
| Cache read | $0.015 | $0.00429 | 0.286 |
The ratio of 0.286 corresponds to a 71.4% difference from the listed official input and output rates. It does not guarantee the same reduction on an invoice with different billing conditions. The OneMux model page lists the snapshot rates; check current OneMux pricing and provider terms for changes.
The example assumes:
- One document per request, including the extraction instructions and schema in the 3,000 input tokens.
- A 400-token response, including JSON keys and any generated overhead billed as output.
- 5,000 requests per day for exactly 30 days, or 150,000 requests.
- No caching, retries, tool-call rounds, or extra fees in the baseline.
- All tokens are billed at the displayed rates; no applicable tier or minimum charge changes the calculation. The supplied Flash catalogue lists no tiers, which is not proof that every route has identical terms.
These token counts are illustrative. Measure them on representative documents; character counts and document pages are not reliable substitutes for billed token usage.
Reproduce the monthly calculation
For any workload, multiply input tokens by the input rate and output tokens by the output rate, dividing each result by one million. Add the two amounts, then multiply by the number of requests.
| Calculation | Official rates | OneMux rates |
|---|---|---|
| Input per request: 3,000 ÷ 1,000,000 × input rate | $0.00045 | $0.0001287 |
| Output per request: 400 ÷ 1,000,000 × output rate | $0.00024 | $0.00006864 |
| Total per request | $0.00069 | $0.00019734 |
| Total for 150,000 requests | $103.50 | $29.601 |
Equivalently, the month contains 450 million input tokens and 60 million output tokens. At official rates, those cost $67.50 and $36.00 respectively. At OneMux rates, they cost $19.305 and $10.296. Keeping input and output separate matters: output costs four times as much per token at both sets of rates.
To compare another model, apply its input and output rates to the same token counts, then check whether different prompts, response lengths, or context tiers make that assumption realistic. Price alone does not establish extraction accuracy.
Account for cache reads and retries
A cache-read rate is not a blanket discount on every input token. It applies only when the route supports caching and the tokens meet its eligibility and billing rules. The supplied Future AGI page lists a cached-input price but does not advertise prompt caching as a capability. Confirm actual support, cache-write charges, minimums, and matching rules for your chosen endpoint before using cache savings in a budget. Unknown charges are not zero.
For arithmetic only, suppose exactly half of the 450 million monthly input tokens are eligible cache reads, with the other half billed as ordinary input. Assume no separate cache-write charge:
| Monthly charge | Official rates | OneMux rates |
|---|---|---|
| 225M ordinary input tokens | $33.75 | $9.6525 |
| 225M cache-read tokens | $3.375 | $0.96525 |
| 60M output tokens | $36.00 | $10.296 |
| Total | $73.125 | $20.91375 |
Schema instructions repeated across requests may be a candidate for caching, but a cache hit depends on provider-specific rules. Do not assume that the changing document text is cached.
Retries move the estimate in the other direction. If 5% of baseline requests each require one additional full-size call, there are 7,500 extra calls. With no caching, that adds $5.175 at official rates or $1.48005 at OneMux rates, for totals of $108.675 and $31.08105. Real retries may have different input and output lengths; measure them separately.
Use JSON Schema validation in the extraction workflow
The Future AGI page reports structured-output support for the Fireworks AI listing, but does not establish extraction accuracy or document the precise schema parameters for every endpoint. OneMux offers an OpenAI-compatible API; structured-output compatibility depends on the selected endpoint and its documented parameters. Verify support before relying on provider-side enforcement.
A practical workflow is:
- Define a small schema with required fields, types, and explicit handling for missing values. For example, require an invoice identifier as a string and allow a due date to be a string or null.
- Send the document with instructions to return only the specified fields. Keep the schema and instructions in the measured input-token total.
- Parse the response and validate it locally with a JSON Schema validator. Reject malformed JSON, missing required fields, and wrong types.
- Check business rules separately. A schema-valid date can still be the wrong date from the document; a valid number can still have the wrong currency.
- Record input and output usage, validation failures, retries, and accepted records. Calculate cost per accepted record as well as cost per request.
For example, if a response omits a required invoice identifier, validation should fail rather than silently insert a guess. Route repeated failures or ambiguous source documents for review. Cap retries so a difficult document cannot consume an unbounded budget.
What the estimate cannot tell you
The source reports a 1,048,576-token context window for the Fireworks AI listing, but a large context limit is not an accuracy guarantee or an instruction to fill it. Check the chosen endpoint's input and output limits and how they interact. The supplied source reports no public benchmark scores for this model, so extraction quality, latency, and failure rates remain unknown here.
Before committing volume, run your own representative evaluation without treating this illustrative calculation as a paid test result. Include short and long documents, missing fields, and ambiguous values; compare validated accuracy and total cost per accepted record across any candidate routes.
Conclusion
Start with $103.50 versus $29.601 as a reproducible 150,000-request baseline, not a forecast. Replace the assumptions with observed usage, then add eligible cache reads, retry costs, and any route-specific charges. Local schema validation and business-rule checks are essential to make the resulting cost meaningful.
Sources
- Future AGI: MiniMax M3.1 Flash on Fireworks AI — reported rates, context and capability listing; page states pricing was verified October 22, 2026.
- OneMux: MiniMax M3.1 Flash — published model listing; catalogue snapshot captured November 12, 2026.
Published price snapshot
Captured 2026-11-12T17:00:05.991Z from the OneMux published catalogue. Prices retain website billing units; this is not a live benchmark. Tiered, cached or time-based billing may differ. Unknown values are not zero.
| Model | Official input | Official output | OneMux input | OneMux output | Published price ratio |
|---|---|---|---|---|---|
| MiniMax M3.1 Flash | $0.15 | $0.6 | $0.0429 | $0.1716 | 0.286 |
Current OneMux prices. Compare workload costs only when input/output and billing units match; see each model page for tier conditions.
FAQ
How much does MiniMax M3.1 Flash cost for 150,000 extraction requests?
At 3,000 input and 400 output tokens per request, the illustrative token cost is $103.50 at the cited official rates or $29.601 at the November 12, 2026 OneMux snapshot rates, before retries, caching, and other charges.
Does JSON Schema validation guarantee accurate extraction?
No. Schema validation checks structure and declared constraints, not whether a value was extracted correctly from the source document. Apply business-rule checks and review ambiguous cases.
Can I assume cached-input pricing for repeated extraction prompts?
No. Confirm that the selected endpoint supports caching and that the repeated tokens meet its cache-read rules. The illustrative cache calculation also excludes any separate cache-write charge.
Related articles
Guides
Qwen4 Max API Cost Guide for JSON Schema Extraction
Estimate Qwen4 Max extraction costs per document and per 100,000 documents, including retries, cache assumptions, and JSON schema validation.
Guides
GPT Image 2.6 Sunburst API costs for structured extraction: a planning guide
Estimate an image-to-JSON workload with explicit token assumptions, schema validation, retries, and pricing limitations.
Guides
GPT Image 2.6 Flare API cost estimates for schema-validated extraction
Build a reproducible API budget for structured extraction, while separating documented image-token rates from unknown extraction and OneMux prices.
Guides
Qwen3.8 Flash API Cost for JSON Extraction: A Reproducible Estimate
Estimate Qwen3.8 Flash API costs for structured extraction, including token usage, schema validation, retries, and a comparison of published rates.