90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
inclusionAI's Ling 3.1 Flash against OpenAI's GPT-6.1 Sol: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
Ling 3.1 Flash lists at $0.112 per million tokens blended against $4.00 for GPT-6.1 Sol - 36x less.
GPT-6.1 Sol scores 55 on the intelligence index against 41 - 13 points apart.
GPT-6.1 Sol reads 1.1M tokens at once, Ling 3.1 Flash 1M.
only GPT-6.1 Sol offers image input.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | Ling 3.1 Flash | GPT-6.1 Sol |
|---|---|---|
| Input price / 1M tokens | $0.07 | $2.00 |
| Output price / 1M tokens | $0.23 | $10.0 |
| Blended (3 in : 1 out) | $0.11 | $4.00 |
| Cached input / 1M | $0.01 | $0.10 |
| Context window | 1M | 1.1M |
| Max output | 262K | 128K |
| Input | text | file, image, text |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 41 | 55 |
| Coding index | - | - |
| Agentic index | - | - |
| Released | Oct 2, 2026 | Sep 29, 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 | Ling 3.1 Flash | GPT-6.1 Sol | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $2.63 | $90.00 | $87.38 less on Ling 3.1 Flash |
| Document summaries100M in, 5M out - long inputs, short answers. | $8.63 | $250 | $241 less on Ling 3.1 Flash |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $9.00 | $320 | $311 less on Ling 3.1 Flash |
Ling 3.1 Flash takes the short and general requests - at $0.112 blended it is the default - and GPT-6.1 Sol the ones whose complexity or quality floor rules the cheaper model out. The split is per request, not per app, and every decision carries the scores for both.
# targets.yaml - both models as routing targets (metadata.model links each to the catalogue entry)
targets:
- { id: ling-3.1-flash, kind: llm, metadata: { model: inclusionai/ling-3.1-flash } }
- { id: gpt-6.1-sol, kind: llm, metadata: { model: openai/gpt-6.1-sol } }
# 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: [ling-3.1-flash]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [gpt-6.1-sol]
weight: 0.8Every inclusionAI and OpenAI model, with prices, is on the vendor pages; the rankings show what the router actually picks.