What will it cost to run this agent
Illustrative model, not a quote. Pick a model, an infrastructure, data + retrieval + gateway posture. Set your user + call volume + human review rate. Get a monthly estimate, with a full breakdown across model, infra, storage, retrieval, gateway and HITL, grounded in vendor-published rates.
- Batch + streaming discounts: model providers offer 40-50% off for async workloads
- Cached input pricing: Anthropic/OpenAI cache tiers change TCO dramatically for high-context agents
- Multi-model routing: RouteLLM / Mixture-of-Agents estimates with per-tier fallback
- Egress + network: cross-region data transfer, CDN, edge inference deltas
- Compliance overhead: sovereignty add-ons (EU-only, HIPAA, FedRAMP) shift infra multipliers
- Compare mode: save two configurations and diff their cost curves as volume scales 10× → 100×
How is the monthly cost of an AI agent calculated?
Seven lines summed: model inference, infrastructure, storage, retrieval, an optional gateway markup, scheduled jobs and human review. Inference is calls per month x tokens per call x the vendor's published per-token rate, counted separately for input and output. The others are either a fixed monthly figure or a per-event rate x volume.
How are token costs worked out?
Tokens divided by one million, multiplied by the published price per million, done separately for input and output because output usually costs several times more. Rates come from the model catalogue, which carries each vendor's own published figures. A model with no published rate falls back to a conservative default rather than a guess.
How is human review priced?
Calls per month x the review rate you set x a per-review cost of $2.20, a mid-market fully-loaded rate. It is deliberately volume-sensitive rather than a fixed overhead, which is why moving the review percentage moves the total more than changing model does. Substitute your own loaded cost per review for a real estimate.
Where do the prices come from?
Vendor-published rates only. Model prices come from the foundation-model table, infrastructure from the cloud table, each row carrying its own source link and verified date. The only exception is a model with no published rate, which falls back to a conservative default rather than a guess.
What does the estimate leave out?
Batch and streaming discounts, cached-input pricing, multi-model routing, cross-region egress, and compliance overheads such as EU-only, HIPAA or FedRAMP infrastructure. Each of those moves a real bill materially, so treat the total as an order of magnitude for comparison, not a quote.
Why does the total change so much when I adjust review?
Because inference is cheap and oversight is not. At realistic review rates a supervised agent spends more on the person checking its work than on the tokens it generates, so the review slider dominates the total. That relationship is the main thing this tool exists to show.