90 days of the enterprise, pro and team plans free, no card needed. See the plans
Best models
Every model in the live reference catalogue with published weights, ranked by the intelligence index (Artificial Analysis, 0-100) with vendor list prices per million tokens. 12 qualify today.
Strongest first; price breaks ties. Value is index points per blended dollar. Click a model for its full specification, or compare two side by side.
| # | Model | Intelligence index | Input / 1M | Output / 1M | Context | Value | Compare |
|---|---|---|---|---|---|---|---|
| 1 | 46 | $0.43 | $0.87 | 1.1M | 85 | ||
| 2 | 45 | $0.08 | $1.40 | 1.0M | 109 | vs MiMo-V2.6-Pro | |
| 3 | 44 | $1.00 | $2.70 | 1.0M | 31 | vs MiMo-V2.6-Pro | |
| 4 | 44 | $0.24 | $11.9 | 1.0M | 14 | vs MiMo-V2.6-Pro | |
| 5 | 42 | $0.15 | $0.50 | 1.0M | 176 | vs MiMo-V2.6-Pro | |
| 6 | 40 | $2.00 | $6.00 | 1.0M | 13 | vs MiMo-V2.6-Pro | |
| 7 | 40 | $0.15 | $0.60 | 1.0M | 150 | vs MiMo-V2.6-Pro | |
| 8 | 38 | $0.14 | $0.28 | 1.1M | 217 | vs MiMo-V2.6-Pro | |
| 9 | 36 | $0.66 | $1.98 | 1.0M | 36 | vs MiMo-V2.6-Pro | |
| 10 | 35 | $0.22 | $0.65 | 1.0M | 108 | vs MiMo-V2.6-Pro | |
| 11 | 34 | $0.04 | $0.13 | 1.0M | 515 | vs MiMo-V2.6-Pro | |
| 12 | 34 | $0.04 | $1.35 | 1M | 92 | vs MiMo-V2.6-Pro |
Open weights change the question from 'what does it cost' to 'what does it cost to run': you pay for hardware and operations, and the data never leaves your network. Only models whose weights are published qualify here; the list price shown is what hosted providers charge for the same weights, a useful floor for what self-hosting has to beat.
The strongest open-weight models now sit close to the closed frontier on the intelligence index, and they are the only answer for a data boundary a provider's terms cannot cross. The gap that remains is in the hardest reasoning and agentic requests - which is exactly what a router is for.
The usual deployment keeps a self-hosted open-weight model as the default and lets the router escalate to a hosted model only for requests that do not carry restricted data and do need the extra quality. A data-boundary rule pins the sensitive requests on-premises; the rest float to whichever target wins on price and quality. Because the self-hosted target has a real cost too - a GPU-hour divided by the tokens it served - declare it in the catalogue, and the router's savings figures compare like with like instead of treating your own hardware as free.
Declare the models as targets and let the rule send the hard requests to the strongest one and the rest to the best value; the trace names the rule that fired.
# rules.yaml - open-weights: the strongest qualifying model for the hard requests, the best value for the rest
rules:
- name: open-weights-hard
when: { contains_pii: true }
prefer: [mimo-v2.6-pro]
weight: 0.8
- name: open-weights-default
when: { max_complexity: 0.45 }
prefer: [deepseek-v4-flash-0731]
weight: 0.6