90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
Meta's Llama 3.3 70B Instruct against Perplexity's Sonar: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
Llama 3.3 70B Instruct lists at $0.155 per million tokens blended against $1.00 for Sonar - 6.5x less.
Intelligence index 8 against 8: within a point of each other.
Llama 3.3 70B Instruct reads 131k tokens at once, Sonar 127k.
only Llama 3.3 70B Instruct offers tool calls, structured output, open weights; only Sonar offers image input.
Sonar was released about 2 months later.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | Llama 3.3 70B Instruct | Sonar |
|---|---|---|
| Input price / 1M tokens | $0.10 | $1.00 |
| Output price / 1M tokens | $0.32 | $1.00 |
| Blended (3 in : 1 out) | $0.16 | $1.00 |
| Cached input / 1M | - | - |
| Context window | 131K | 127K |
| Max output | 16K | 114K |
| Input | text | text, image |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 8 | 8 |
| Coding index | 12 | - |
| Agentic index | - | - |
| Released | Dec 6, 2024 | Jan 27, 2025 |
| Available on this deployment |
List price times tokens for three typical workloads; your mix of input and output decides which model's pricing suits you.
| Workload | Llama 3.3 70B Instruct | Sonar | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $3.60 | $25.00 | $21.40 less on Llama 3.3 70B Instruct |
| Document summaries100M in, 5M out - long inputs, short answers. | $11.60 | $105 | $93.40 less on Llama 3.3 70B Instruct |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $12.40 | $80.00 | $67.60 less on Llama 3.3 70B Instruct |
The two measure the same on the intelligence index, so the router treats them as peers and lets price, observed latency and your outcomes decide: Llama 3.3 70B Instruct wins on cost, and a few bad outcomes on either move the next requests to the other.
# targets.yaml - both models as routing targets (metadata.model links each to the catalogue entry)
targets:
- { id: llama-3.3-70b-instruct, kind: llm, metadata: { model: meta-llama/llama-3.3-70b-instruct } }
- { id: sonar, kind: llm, metadata: { model: perplexity/sonar } }
# rules.yaml - the cheaper model by default, the stronger one when the request is hard
rules:
- name: simple-requests-stay-cheap
when: { max_complexity: 0.45 }
prefer: [llama-3.3-70b-instruct]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [sonar]
weight: 0.8Every Meta and Perplexity model, with prices, is on the vendor pages; the rankings show what the router actually picks.