AI API pricing by vendor
Every model a vendor ships, with the rate it actually bills at. Use this when you are choosing inside one ecosystem; use the full price index when you are comparing across them.
All vendors
Anthropic API pricing
41 billable models · USD per 1M tokens
Claude is the default choice for agentic coding, long-context document work, and anything where instruction-following quality matters more than raw token cost.
OpenAI API pricing
154 billable models · USD per 1M tokens
GPT-5.6 Luna is the volume workhorse, cheap enough for classification and routing, strong enough for most user-facing chat.
Google API pricing
83 billable models · USD per 1M tokens
Gemini wins on long-context and multimodal work. Flash tiers are among the cheapest capable models available anywhere.
DeepSeek API pricing
41 billable models · USD per 1M tokens
DeepSeek is the default choice when output volume dominates (R1-class reasoning at a fraction of US frontier pricing).
Alibaba API pricing
90 billable models · USD per 1M tokens
Qwen coder models are strong enough for agentic work and priced well below comparable US models.
xAI API pricing
33 billable models · USD per 1M tokens
Grok is competitive on real-time and search-adjacent workloads.
Zhipu API pricing
32 billable models · USD per 1M tokens
GLM-5.x is a strong general-purpose Chinese-language model with competitive agentic performance.
Moonshot API pricing
18 billable models · USD per 1M tokens
Kimi is the usual pick when you need a long context window without frontier-model pricing.
Meta API pricing
26 billable models · USD per 1M tokens
Llama 405B is the usual open-weight choice when you need on-prem-equivalent capability without a frontier price tag.
MiniMax API pricing
7 billable models · USD per 1M tokens
MiniMax is competitive for high-volume chat and character-style applications.
ByteDance API pricing
47 billable models · USD per 1M tokens
Doubao is widely used for high-volume Chinese-language workloads.
Every vendor side by side
Choosing inside one ecosystem is a different problem from choosing across them. The table below is the across-them view: it answers "how deep does this vendor's catalogue go, where is its price floor, and how aggressively does it price output". The three questions that decide whether a vendor is worth a closer look.
| Vendor | Billable models | Cheapest input / 1M | Cheapest output / 1M | Median output ÷ input | With published list price |
|---|---|---|---|---|---|
| Anthropic | 20 | $0.05 | $0.25 | 5.0× | 13 |
| OpenAI | 84 | $0.025 | $0.2 | 6.0× | 4 |
| 21 | $0.0375 | $0.15 | 5.0× | 0 | |
| DeepSeek | 34 | $0.14495 | $0.217425 | 4.0× | 0 |
| Alibaba | 47 | $0.025 | $0.1 | 4.0× | 0 |
| xAI | 30 | $0.1 | $0.25 | 3.0× | 0 |
| Zhipu | 11 | $0.075 | $0.25 | 3.2× | 0 |
| Moonshot | 12 | $0.3 | $1.2 | 4.1× | 0 |
| Meta | 11 | $0.05 | $0.0625 | 2.0× | 0 |
| MiniMax | 7 | $0.075 | $0.3 | 4.0× | 0 |
| ByteDance | 30 | $0.015 | $0.15 | 5.6× | 0 |
"Billable models" is the count after removing legacy generations, non-chat variants and resold entries, the set you can actually put side by side. The last column counts models carrying a published vendor list rate we could verify; the rest are shown at face value with no comparison implied.
The median output-to-input multiple is the column people skip and then get surprised by. A vendor whose floor looks attractive on input can charge four or five times that on output, which matters more the more text your workload generates. Across the 226 models in our cleaned catalogue the median is 4.0× and the widest is 12.0×, so the spread between vendors on this one dimension is larger than the spread on headline input rates.
Why the vendor pages exist
A vendor's own pricing page is usually a marketing summary It shows the flagship model and leaves out the legacy tiers still running in production, the regional variants, and the output multiples that dominate real bills. These pages list the full billable catalogue instead, because that is the only way to tell whether the tier you picked is the tier you meant to pick.
Rates are synced from the gateway's pricing endpoint and verified against vendor documentation where a stable published source exists. Where we could not verify, we say so on the row rather than inventing a comparison.