Input price
What the maker charges per million tokens you send: instructions, documents, images, tool definitions and conversation history.
Why it matters. Dominates the bill for long-document and agent work, where the same context is re-sent many times.
How it works
The input price is the rate charged for every token in the request, quoted on this site in USD per 1 million tokens. It covers the system prompt, user messages, earlier turns, attached files and images (after conversion to tokens), and tool definitions and results.
Most makers discount input tokens read from a prompt cache, and some charge a higher rate for very long prompts. Rates can also differ between the maker's own API and cloud platforms, and between standard, batch and priority tiers.
In chat and agent workloads the same context is re-sent on every turn, so input often outweighs output on the bill even though each output token costs more. Track input tokens per task, not just per call.
Worked example
At an illustrative $3 per 1M input tokens, a 20K-token prompt costs 20,000 / 1,000,000 x $3 = $0.06. An agent that re-sends that 20K context over 30 turns pays about $1.80 in input alone, before any caching.
Common mistakes
- Estimating cost per call rather than per task, missing how agent loops re-send context.
- Forgetting that tool definitions and images count as input tokens on every request.
- Comparing list input prices without accounting for cache discounts and long-context rates.
Across the catalog today
See it on a real card: Pricing & cost on Claude Opus 5.5.
Related terms
- Pricing08
Output price
Cost per 1M tokens the model generates
Explained - Basics01
Token
The unit models read, write and bill by
Explained - Pricing09
Prompt caching
Discounted reuse of a repeated prompt prefix
Explained - Pricing10
Long-context pricing
Higher rates once a prompt passes a set length
Explained - Pricing11
Batch API
Async bulk requests at a discount
Explained