Agent cost & context calculator
An agent loop re-sends its whole conversation every turn, so cost grows with the square of turn count. See what your loop actually costs, and what caching changes.
List prices as published, June 2026. Editable below — check against current pricing before quoting anything.
The stable prefix, sent on every single turn. This is what caching is for.
User message plus tool results. Tool results are usually the larger half.
What the model generates, including its thinking.
The agent loop depth. This is the number that changes the arithmetic.
How many times this runs across the business.
Per session
$1.97
347K in · 9.6K out
Per day
$987
500 sessions
Per month
$29,610
30 days at this volume
What you are paying to send
- 3% new content
- 97% re-sent history
Without caching
$29,610
per month
With caching
$11,166
per month · 62% less
Context at the final turn
54K of 1.00M
Critical
97% of input tokens are re-sent conversation history
The API is stateless, so every turn re-sends everything before it. Across 12 turns that is 347K of input for 11K of genuinely new content on turn one. Input cost grows with the square of turn count, not linearly — which is why an agent that is affordable in a three-turn demo is a different product at 12.
Worth knowing
Prompt caching is off
Enabling it would take this session from $1.97 to $0.74 — 62% less. Caching is a prefix match: any byte that changes early invalidates everything after it, so a timestamp or a per-request ID near the top of the system prompt silently disables it and nothing errors.
Prices are list prices as published in June 2026 and are editable above — they will drift, and this page is not a price list. The arithmetic is the durable part: input cost grows with the square of turn count because the API is stateless and every turn re-sends the whole conversation. That is the shape most agent budgets get wrong, at any price.
Other tools
- EDI viewer & validator (X12 + EDIFACT)
- X.509 certificate decoder
- JSON ↔ XML converter
- CSV ↔ JSON converter
- OpenAPI linter
- MCP tool-definition linter
- OpenAPI → agent tools
- Agent blast-radius calculator
- Prompt secret scanner
- Agent-readiness scorecard
- iPaaS readiness assessment
- Modernisation roadmap generator
- Migration risk register
- Cutover runbook builder
- Interface catalogue builder
- Migration wave planner
- Function Point estimator
- Platform migration assessor
- Fixed-width flat file parser
- webMethods flow reader
- SAP IDoc viewer
- SWIFT MT & ISO 20022 viewer
- HL7 v2 message viewer
- XSLT tester
- XPath tester
- CI/CD workflow security linter
- Regex tester & ReDoS checker
- Webhook signature verifier
- SLA & error budget calculator
- Retry & backoff simulator
- JSONPath tester
- JSON Schema generator
- Encoding & mojibake fixer
- JSON formatter & validator
- JSON diff
- Epoch & timestamp converter
- Base64 encoder & decoder
- UUID & ULID generator
- JWT decoder
- Cron expression explainer
- Interface math calculator
- Post-quantum migration matrix
- Post-quantum exposure calculator
These exist because the underlying problem is real. If the numbers you just put in look uncomfortable, that is usually worth a conversation.