Three Reproducible AI Cost Scenarios: Support, RAG, and Agents

Cost advice is only useful when the assumptions are visible. This article publishes three simulated workloads — customer support, retrieval-augmented generation, and a multi-step agent — with enough information to reproduce every result. These are not customer results and they are not claims about typical savings. They are worked examples showing how request volume, fresh input, cached input, output, and agent steps change the arithmetic.

All three scenarios use the dated GPT-5.6 Luna reference rates stored by TokenCostAI: USD 1.00 per million fresh input tokens, USD 0.10 per million cached input tokens, and USD 6.00 per million output tokens. The price row was manually approved on 2026-08-22 with the official OpenAI pricing page recorded as its source. Provider prices and cache eligibility can change, so verify the current official terms before using the results for procurement.

The calculation used in every scenario

Monthly cost = ((fresh input tokens × input rate) + (cached input tokens × cached-input rate) + (output tokens × output rate)) ÷ 1,000,000. Token counts are monthly totals. For agent scenarios, monthly calls = agent runs × average steps per run.

A percentage change below describes only the two stated simulations. It is not a promised saving for another application.

Scenario 1: customer-support drafting

Baseline assumptions: 100,000 requests per month; 1,500 fresh input tokens and 300 output tokens per request; no cached input. Monthly input is 150 million tokens and output is 30 million tokens. The calculation is (150 × USD 1.00) + (30 × USD 6.00) = USD 330.00 per month.

Alternative assumptions: the same 100,000 requests; 300 fresh input tokens, 600 cache-eligible input tokens, and 150 output tokens per request. Monthly cost is (30 × USD 1.00) + (60 × USD 0.10) + (15 × USD 6.00) = USD 126.00. The difference between these two simulations is USD 204.00, or 61.8%. Real cache hits, response quality, and support-message length must be measured before adopting this design.

Scenario 2: reducing RAG context

Baseline assumptions: 50,000 questions per month; 6,000 fresh input tokens and 400 output tokens per question. Monthly cost is (300 × USD 1.00) + (20 × USD 6.00) = USD 420.00.

Alternative assumptions: retrieval and reranking reduce fresh input to 2,500 tokens while output remains 400 tokens. Monthly cost is (125 × USD 1.00) + (20 × USD 6.00) = USD 245.00. The difference is USD 175.00, or 41.7%. This example does not include embedding, vector storage, or reranker charges; those costs must be added for a complete architecture comparison.

Scenario 3: limiting an agent loop

Baseline assumptions: 20,000 agent runs per month; eight model steps per run; 2,500 fresh input tokens and 300 output tokens per step. That produces 160,000 model calls, 400 million input tokens, and 48 million output tokens. Monthly model cost is (400 × USD 1.00) + (48 × USD 6.00) = USD 688.00.

Alternative assumptions: four steps per run after adding a step limit and compact state summary; 1,500 fresh input tokens and 200 output tokens per step. That produces 80,000 calls, 120 million input tokens, and 16 million output tokens. Monthly model cost is (120 × USD 1.00) + (16 × USD 6.00) = USD 216.00. The difference is USD 472.00, or 68.6%. This comparison assumes task quality remains acceptable, which must be tested rather than inferred from cost alone.

Copyable scenario inputs

Support baseline: requests=100000, input=1500, cached=0, output=300. Support alternative: requests=100000, input=300, cached=600, output=150. RAG baseline: requests=50000, input=6000, cached=0, output=400. RAG alternative: requests=50000, input=2500, cached=0, output=400. Agent baseline: calls=160000, input=2500, cached=0, output=300. Agent alternative: calls=80000, input=1500, cached=0, output=200. In the calculator, input and cached input are separate fields; do not include the cached portion again in the input field.

Download the frozen scenario inputs and expected totals. A local verification script recalculates every monthly total and pairwise percentage from that file before the site build is packaged.

How to use these examples responsibly

• Replace the example request counts with measured or explicitly forecast volume.
• Use provider-reported token counts when available; character-based estimates are only planning approximations.
• Measure cache hit rate and confirm which tokens qualify for the provider cache tier.
• Add non-token charges such as embeddings, storage, reranking, observability, and retries.
• Compare answer quality and task completion rate alongside cost.

You can reproduce the arithmetic with the TokenCostAI calculator and review how the reference dataset is maintained on the methodology page. If your result differs, send the exact inputs through the contact page so the calculation can be checked.