llmcloud.ai
Model catalog

Every model. One search box.

Filter across frontier and open-source models by modality, org, context, and price. Point at any model with a single string like anthropic/claude-opus-4.5.

Max $/1M out:$20.0
Showing 125 of 161 (161 total)
Modality
anthropic/claude-opus-4.5Anthropic94.282320ms200k$15.00
textvision
openai/gpt-5.5OpenAI93.874410ms400k$12.50
textvisionaudio
anthropic/claude-opus-4.1Anthropic93.178340ms200k$15.00
textvision
openai/gpt-5OpenAI92.478420ms400k$10.00
textvisionaudio
google/gemini-3.1-proGoogle92.1118180ms2000k$7.00
textvisionaudiovideo
openai/gpt-5-codexOpenAI91.296260ms400k$4.50
text
anthropic/claude-sonnet-4.5Anthropic90.8118220ms200k$3.00
textvision
xai/grok-5xAI90.695260ms256k$6.00
textvision
google/gemini-2.5-proGoogle90.4108210ms2000k$5.00
textvisionaudiovideo
openai/o3OpenAI90.162520ms200k$10.00
textvision
deepseek/deepseek-v4DeepSeek89.9140210ms128k$0.55
text
anthropic/claude-sonnet-4Anthropic89.4122210ms200k$3.00
textvision
alibaba/qwen3-coder-480bhostedAlibaba89.4130220ms256k$1.20
text
xai/grok-4xAI89.190280ms256k$5.00
textvision
alibaba/qwen3-235b-thinkingAlibaba88.982340ms128k$0.90
text
alibaba/qwen3-maxAlibaba88.4128240ms1000k$0.90
textvision
moonshot/kimi-k2-thinkingMoonshot88.482360ms256k$3.00
text
openai/gpt-4.1OpenAI88.292300ms1000k$8.00
textvision
deepseek/deepseek-r1DeepSeek88.290320ms128k$0.55
text
deepseek/deepseek-coder-v3DeepSeek88.2155200ms128k$0.60
text
anthropic/claude-sonnet-3.7Anthropic88.1128200ms200k$3.00
textvision
meta/llama-4-405bMeta87.6165150ms128k$2.40
textvision
openai/o4-miniOpenAI87.588380ms200k$1.10
textvision
deepseek/deepseek-v3.2-exphostedDeepSeek87.1150200ms128k$0.28
text
alibaba/qwen3-vl-235bhostedAlibaba87.076380ms128k$2.00
textvision

How to read the catalog

Every row is a model as it is actually served, not as it was announced. Prices are USD per million tokens at provider list — llmcloud adds no margin, so the number you see is the number you are billed. Where several providers serve the same weights, the catalog shows the best currently available combination and the router picks between them per request.

Context

The usable window under real concurrency, including KV cache headroom — not the architectural maximum quoted at launch.

Throughput

Median decode tokens per second per stream, measured by our probes rather than taken from vendor marketing.

TTFT

Time to first token at p50 from our edge. This dominates perceived speed in interactive products far more than total throughput.

Quality

A blended score across task-class evals, refreshed daily. Use it to shortlist, then confirm on your own traffic.

Modality

What the endpoint actually accepts today. A model with vision weights is only listed as vision if the served endpoint takes images.

Price

Input and output rates listed separately because the blend depends entirely on your workload. Reasoning traces bill as output tokens.

Picking a model without guessing

Headline benchmark scores are the worst way to choose. Three numbers in this table predict production outcomes far better: blended price at your real input-to-output ratio, p50 time to first token from your users' region, and the model's failure mode on malformed tool calls. A model two points down on a leaderboard but half the price and 300 ms faster is usually the better production choice, which is exactly the tradeoff smart routing automates. For per-task evidence, read the live leaderboard, or the workload playbooks.

Model catalog FAQ

Does llmcloud mark up token prices?

No. Tokens are billed at provider list price with no platform fee and no credit float. Revenue comes from Team seats at a flat 10 USD per user per month and from hosted inference on our own hardware.

Why do two providers show different prices for the same model?

Because they run different serving configurations, hardware, and margins on identical open weights. That spread is the reason routing exists — the router picks per request based on live price, latency, and success rate rather than a fixed vendor preference.

How often is the catalog updated?

Prices and availability are polled from provider manifests continuously; latency and throughput figures refresh from probe data through the day; quality ranks recompute daily. New model launches are added once they pass the compatibility suite.

Are quantized builds labelled?

Yes. Served precision is a published field and providers agree during certification not to substitute a quantized or different build under a name implying the reference weights. Violations remove a provider from the pool.

Can I restrict my organisation to a subset of this catalog?

Yes. API keys carry allow-lists for models, routing policies, providers, and regions, so a staging key can be limited to cheap models while a production key is limited to zero-retention providers in a single jurisdiction.