Model pricing
Rates are read off each provider’s own pricing documentation and shown with the date they were checked. For the 12 of 31 models that are also in the live model catalog Spendline uses to price API traffic, our automated checks compare the two and fail if they disagree; those are marked “Matched to live catalog”. The rest are marked “Publisher documentation only”.
These are model-provider rates, not Spendline fees. Start with a guided 30-day free pilot on live production traffic. The 30 days start when your traffic flows through Spendline, not at sign-up. We agree the scope, success criteria and paid terms before you start. There is no Spendline subscription fee during the pilot; your model-provider charges still apply. Book a 30-minute call.
Providers change rates and the old number disappears. We keep a dated log of every price change we have observed, including the ones that have been announced but have not taken effect yet.
Every page here shows a rate card, and a rate card is the smallest part of what a team actually pays. Output usually costs several times input, so responses drive the invoice even when prompts look larger. Reasoning tokens bill as output, which means raising an effort setting raises the bill without changing a prompt. Retries and agent fan-out pay full price for calls that produced nothing. And provider reports group usage by model, project or API key. Your application supplies the customer and workflow context needed to see cost per account.
The guides go into that in depth: what Claude actually costs and why the token estimate comes in low, how to track LLM costs per customer, and LLM unit economics.