90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
DeepSeek's DeepSeek V4.1 Flash 1017 against OpenAI's GPT-5.4: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
DeepSeek V4.1 Flash 1017 lists at $0.262 per million tokens blended against $5.63 for GPT-5.4 - 21x less.
Intelligence index 40 against 39: within a point of each other.
GPT-5.4 reads 1.1M tokens at once, DeepSeek V4.1 Flash 1017 1.0M.
only DeepSeek V4.1 Flash 1017 offers open weights.
DeepSeek V4.1 Flash 1017 was released about 8 months later.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | DeepSeek V4.1 Flash 1017 | GPT-5.4 |
|---|---|---|
| Input price / 1M tokens | $0.15 | $2.50 |
| Output price / 1M tokens | $0.60 | $15.0 |
| Blended (3 in : 1 out) | $0.26 | $5.63 |
| Cached input / 1M | $0.003 | $0.25 |
| Context window | 1.0M | 1.1M |
| Max output | 393K | 128K |
| Input | text, image | text, image, file |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 40 | 39 |
| Coding index | - | 71 |
| Agentic index | - | - |
| Released | Oct 17, 2026 | Mar 5, 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 | DeepSeek V4.1 Flash 1017 | GPT-5.4 | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $6.00 | $125 | $119 less on DeepSeek V4.1 Flash 1017 |
| Document summaries100M in, 5M out - long inputs, short answers. | $18.00 | $325 | $307 less on DeepSeek V4.1 Flash 1017 |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $21.00 | $450 | $429 less on DeepSeek V4.1 Flash 1017 |
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: DeepSeek V4.1 Flash 1017 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: deepseek-v4.1-flash-1017, kind: llm, metadata: { model: deepseek/deepseek-v4.1-flash-1017 } }
- { id: gpt-5.4, kind: llm, metadata: { model: openai/gpt-5.4 } }
# 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: [deepseek-v4.1-flash-1017]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [gpt-5.4]
weight: 0.8Every DeepSeek and OpenAI model, with prices, is on the vendor pages; the rankings show what the router actually picks.