90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
OpenAI's GPT-4.1 Nano against Upstage's Solar Pro 3: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
GPT-4.1 Nano lists at $0.175 per million tokens blended against $0.262 for Solar Pro 3 - 1.5x less.
Intelligence index 8 against 8: within a point of each other.
Solar Pro 3 scores 16 on the coding index against 11 - 5 points apart.
GPT-4.1 Nano reads 1.0M tokens at once, Solar Pro 3 131k.
only GPT-4.1 Nano offers image input; only Solar Pro 3 offers reasoning.
Solar Pro 3 was released about 10 months later.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | GPT-4.1 Nano | Solar Pro 3 |
|---|---|---|
| Input price / 1M tokens | $0.10 | $0.15 |
| Output price / 1M tokens | $0.40 | $0.60 |
| Blended (3 in : 1 out) | $0.18 | $0.26 |
| Cached input / 1M | $0.03 | $0.01 |
| Context window | 1.0M | 131K |
| Max output | 943K | 118K |
| Input | image, text, file | text |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 8 | 8 |
| Coding index | 11 | 16 |
| Agentic index | - | 1 |
| Released | Apr 14, 2025 | Jan 27, 2026 |
| 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 | GPT-4.1 Nano | Solar Pro 3 | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $4.00 | $6.00 | $2.00 less on GPT-4.1 Nano |
| Document summaries100M in, 5M out - long inputs, short answers. | $12.00 | $18.00 | $6.00 less on GPT-4.1 Nano |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $14.00 | $21.00 | $7.00 less on GPT-4.1 Nano |
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: GPT-4.1 Nano 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: gpt-4.1-nano, kind: llm, metadata: { model: openai/gpt-4.1-nano } }
- { id: solar-pro-3, kind: llm, metadata: { model: upstage/solar-pro-3 } }
# 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: [gpt-4.1-nano]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [solar-pro-3]
weight: 0.8