Blended cost depends on your input:output ratio
Output usually costs 3-4x input. Two models with the same input rate can differ 2x on a real workload, so your token split matters more than the headline price.
Real LLM API prices, in USD and CHF. Every number is sourced, and when a rate comes from billing data instead of a pricing page, we say so. Mostly measured on Microsoft Foundry (formerly Azure AI Foundry), plus direct APIs to compare against.
One page each: the full table in USD and CHF, plus the quirks a pricing page hides, like cache meters, Responses-API-only models, and deployment-tier premiums.
Kimi K3 is a 1M-context flagship, now on Microsoft Foundry as well as Moonshot's own API; earlier K2 models are resold on Foundry across tiers.
1M-token context, cheap direct pricing, and Microsoft Foundry resale markups from ~10% to a reported 4.5x — with one Data Zone lane that undercuts Global.
GLM-5.3-Flash adds a multimodal, half-price direct lane, while GLM-5.3, 5.1 and 5.2 remain aligned on the full-rate tier.
Azure normally resells OpenAI 1:1, but a promotional cut on the GPT-5.6 Sol flagship has opened a fresh gap. Deployment type and Responses-API-only variants are the other catches.
Claude Fable 5.1's 1M-token frontier lane, Sonnet 5's permanent launch pricing, cheaper cache reads, and Azure CCU billing on Microsoft Foundry.
Gemini 3.7 Flash is the new flagship, and Gemini 3.6 Flash's price is halved to match it — both $0.75/$0.075/$3.75 per M through year-end.
Grok 4.6 is direct-API only for now; Microsoft Foundry resells the 4.x line up to Grok-4.3, which now carries a published cache meter.
Qwen3.8 Max is the flagship, while Qwen3.8 Flash adds a new $0.15/$0.47 multimodal direct lane — but Foundry still has no per-token Qwen meter.
Mistral Medium 3.5 is now on Microsoft Foundry at the same rate as Mistral's own API.
MiniMax M2.5 and MiniMax 3 are resold on Microsoft Foundry as Data Zone-only serverless listings; the direct API adds M2.7 and M3 as the current lineup for comparison.
The retrieval layer. Input-only pricing, and the cheapest model is rarely the right one for code RAG.
Seven things that decide what you actually pay. None of them is the headline number.
Six steps for finding what a workload really costs, including how to back out an undocumented cache rate from a billing export.
Get the provider's published per-million rate for input, output, and cached input if it's listed.
Run a real workload and read the actual billed cost from Azure Cost Management, not a chat client's estimate.
If real cost is far below the flat-rate math, suspect an undocumented cache discount before assuming a bug.
Export a cost report grouped by meter, not by service name. Match known meters to confirmed rates to back out token counts, then solve for the unknown: cached_rate = cached_meter_cost / cached_token_count.
Cross-check those token counts against the usage dashboards to validate your assumptions.
Treat anything not on an official page as an estimate, not fact. Re-check once real numbers land or a billing cycle closes.