Illustrative p50
Base prompt
600 tokensRetrieved context
4 chunks × 180 tokensEffective input
1,320 tokensOutput
250 tokensEstimate average token load with practical p50 and p90 defaults for agent and retrieval workflows, then replace the assumptions with measured request logs.
How many input and output tokens should I assume per AI request?
Formula: effective_input_tokens = base_prompt_tokens + retrieved_chunks * tokens_per_chunk
Example: base prompt 600 + (4 chunks * 180) gives 1,320 effective input tokens per request.
Use two planning cases for the same workflow: p50 as the median request and p90 as the heavier tail. These are starting assumptions, not universal benchmarks; replace them with measured request logs when available.
| Planning case | Base prompt | Retrieved chunks | Tokens / chunk | Effective input | Output |
|---|---|---|---|---|---|
| Illustrative p50 | 600 | 4 | 180 | 1,320 | 250 |
| Illustrative p90 | 1,000 | 6 | 220 | 2,320 | 350 |
Base prompt
600 tokensRetrieved context
4 chunks × 180 tokensEffective input
1,320 tokensOutput
250 tokensBase prompt
1,000 tokensRetrieved context
6 chunks × 220 tokensEffective input
2,320 tokensOutput
350 tokensThe effective-input column applies the formula above. Keep the model fixed while comparing these cases so the cost change comes from token load rather than a simultaneous pricing change.
Open AI Workflow Cost with the same starter inputs shown above. Switch to Conservative to pressure-test the p90 case, then replace both with measured logs.
Open Workflow Cost CalculatorBack to calculators: Prompt Overhead, AI Workflow Cost