Dated pricing records

Model pricing comparison

Price the same workload under different assumptions rather than comparing model rates in isolation.

Model Pricing Comparison

Compare workload estimates using source-linked OpenAI and Gemini public price records or your custom rates.

Workload
Tasks completed without needing a rerun
Model usage
Source-linked public list pricing; update before planning spend
Agent behavior
Extra requests after failures or incomplete outputs
Traces, logs, evaluation and retention allowance
Optional escalation or quality-review allowance
Visible uncertainty around your chosen assumptions
RAG & tools
Third-party APIs, browser or search services
Embeddings, vector reads and storage allowance

Estimated monthly cost

$0

Planning range: —

↘ Model your drivers
$0.000Cost / request
$0.000Cost / successful task
—Cost / 100 users

Cost breakdown (monthly)

Model tokens$0
Tools & RAG$0
Observability$0
Human review$0
Retries$0
Top driver: model tokens

Try caching stable context to reduce repeated input cost.

⌁ How the estimate works

Monthly cost combines model tokens, tools, RAG, observability, human review and retry behavior from your editable assumptions.

monthly = model + tools + RAG + observability + human review + retries

▣ Sources & assumptions

Rate records are source-linked and versioned. Always check the provider page before final budgeting.

? FAQ

Why can an invoice differ? Contracts, taxes, regional pricing, tool metering and usage behavior can change the final bill.

Use a common workload

Rate cards use different model names, context conditions and tool terms. Hold requests, steps, inputs, outputs, cache share and success rate constant while comparing scenarios. Then inspect what changes quality, latency and operational workload.

Frequently asked questions

Does API list pricing equal my monthly cost?

No. List pricing is one input. Your bill can also reflect output length, cache behavior, retries, tool calls, storage, regional or contract terms, taxes and provider-specific metering.

Why estimate cost per successful task?

Requests that fail, retry, or need manual recovery still consume resources. Cost per successful task connects technical usage to the outcome your product actually delivers.

Can I use custom pricing?

Yes. Select Custom rates in the calculator and enter your own input and output price per million tokens. This is useful for negotiated or provider-specific terms.