Back to calculator Use calculator
AI & AutomationGenerated accuracy model review: 2026-05-06
OpenRouter Cost Calculator accuracy and testing
This page documents how Calwarden builds trust for this calculator: source notes, regression-style default tests, limitations, assumptions, unit handling, rounding, and visible change history.
Formula source
- Base cost is the per-request input and output token cost multiplied by request count. Routing fee is base cost multiplied by the markup percentage. Total cost is base cost plus routing fee.
Test cases
Default input regression check
Generated from the checked-in default inputs and calculate function.
Inputs
- Model Pricing Preset: openai_gpt_5_4_mini
- Input Tokens: 1,000 tokens/request
- Output Tokens: 500 tokens/request
- Input Price Per Million: 1 $/1M tokens
- Output Price Per Million: 3 $/1M tokens
- Request Count: 10,000 requests
- Routing Markup Percent: 0%
Expected outputs
- Total Cost: $30.00
- Base Cost: $30.00
- Routing Fee: $0.00
- Effective Cost Per Request: $0.00
Known limitations
- This page documents the checked-in calculator logic and does not certify results for every real-world edge case.
- Use the result as a planning estimate unless the calculator page states a stricter purpose.
Assumptions
- Token prices are entered manually and treated as flat per-million-token rates.
- Every request uses the same average input and output token counts.
- Routing markup is applied to base token cost only.
- The estimate excludes retries, caching, provider credits, taxes, storage, and non-token fees.
Unit handling
- Model Pricing Preset accepts one of the configured options.
- Input Tokens accepts values in tokens/request.
- Output Tokens accepts values in tokens/request.
- Input Price Per Million accepts values in $/1M tokens.
- Output Price Per Million accepts values in $/1M tokens.
- Request Count accepts values in requests.
- Routing Markup Percent accepts values in %.
- Total Cost is displayed as currency.
- Base Cost is displayed as currency.
- Routing Fee is displayed as currency.
- Effective Cost Per Request is displayed as currency.
Rounding rules
- Number displays use up to 2 decimal places in the calculator UI.
- Currency outputs are displayed with standard US dollar formatting.
- Input precision follows configured step values where provided.
Version history
1.0.0 - 2026-05-06
Generated accuracy and testing page from the current openrouter-cost-calculator calculator definition.
Change log
2026-05-06
Published default regression test documentation and metadata fallbacks for OpenRouter Cost Calculator.
Calculator transparency
Accuracy pages are generated from checked-in calculator definitions and can be upgraded with curated review metadata over time.