Glimpse vs Sonar Reasoning Pro
Updated October 21, 2026. No benchmark has tested both models yet. Coding is ranked on the Vibe Coding Index; every other board is shown as published.
- Coding
- No data
- Overall
- No data
- Output $/M
- $3.00
- Coding
- No data
- Overall
- 11.8
- Output $/M
- $8.00
Decision reading
Neither model has a coding score yet, so the two cannot be ranked on coding.
Glimpse has the edge where output tokens cost 2.7x less, and where the context window is larger, 262K against 128K tokens.
No benchmark has tested both yet. Glimpse has none yet; Sonar Reasoning Pro on AA Intelligence Index. Compare them on price and context instead.
Which one for your work
Each card is decided by one number both models carry. Where only one has it, the card says so and makes no call.
Coding
Vibe Coding Index, six public coding benchmarks
No call
Neither has a coding score yet.
One side not measured
Intelligence
AA Intelligence Index
No call
Only Sonar Reasoning Pro has a AA Intelligence Index result, 11.8.
Directional only
Long documents
Listed context window
Glimpse
Glimpse takes 262K tokens against 128K.
Listed by OpenRouter
Everyday cost
1K input + 500 output tokens
Glimpse
Glimpse $0.0021, Sonar Reasoning Pro $0.0060 per turn.
List prices
At a glance
- Coding index
- Glimpse not benchmarked, Sonar Reasoning Pro not benchmarked.
- Widest category
- None yet: no category has been tested on both models.
- Widest single gap
- None yet: no benchmark has tested both models.
- Output price
- Glimpse $3.00 against Sonar Reasoning Pro $8.00 per million output tokens, 2.7x apart.
- Context window
- Glimpse takes 262K tokens, Sonar Reasoning Pro 128K.
Benchmark by benchmark
Every board either model has a result on, a category to a fold; bars are each result on a 0 to 100 scale. Only one model is measured on each, so no row names a leader.
IntelligenceDirectional onlyPublic boards, shown as published, kept out of the index1 board measured
| Benchmark | Glimpse | Sonar Reasoning Pro | Leader |
|---|---|---|---|
| AA Intelligence Index | Not measured | 11.8 | Only Sonar Reasoning Pro measured |
| Neither model has a result on the other 1 board here | |||
What each workload costs
Three fixed token mixes at each model's listed price, so per-token rates become a bill.
Chat turn
1K input + 500 output tokens
Glimpse costs less
Repository review
50K input + 3K output tokens
Glimpse costs less
Agent loop
200K input + 10K output tokens
Glimpse costs less
Listed OpenRouter rates, without cache or batch discounts. A workload that does not fit a model's context window would need splitting.
Specification differences
The leading value in a row is marked; a row with a missing value names no leader. Our two rows are marked in red.
| Specification | Elorian Glimpse | Perplexity Sonar Reasoning Pro |
|---|---|---|
| Maker | Elorian | Perplexity |
| Weights | No public weights listed | No public weights listed |
| Released | October 17, 2026 | March 7, 2025 |
| Context window | 262K | 128K |
| Input $/Mtok | $0.60 | $2.00 |
| Output $/Mtok | $3.00 | $8.00 |
| Coding index | Not benchmarked | Not benchmarked |
| Independent measurements behind it | 0 | 0 |
| Cost per solved task | Not computable | Not computable |
| Source | OpenRouter listing | OpenRouter listing |
Questions
Is Glimpse better than Sonar Reasoning Pro for coding?
Neither model has a coding score yet, so the two cannot be ranked on coding. Glimpse has the edge where output tokens cost 2.7x less, and where the context window is larger, 262K against 128K tokens.
Which is cheaper, Glimpse or Sonar Reasoning Pro?
Glimpse costs $0.60 per million input tokens and $3.00 per million output tokens; Sonar Reasoning Pro costs $2.00 and $8.00. Cost per solved task is known for neither of them.
Which has the bigger context window, Glimpse or Sonar Reasoning Pro?
Glimpse, with 262K tokens against 128K.
Has any benchmark tested both Glimpse and Sonar Reasoning Pro?
No benchmark has tested both yet. Glimpse has none yet; Sonar Reasoning Pro on AA Intelligence Index. Compare them on price and context instead. Data as of October 21, 2026.