Agentic
Directional only- Agents-A1
- 75.5
- Step 3.7 Flash
- 66.4
- Weighted basis
- 1 vs 2 rows
- Reading
- Directional only
Five or fewer confirmed AI changes, with original sources, on mornings when something changed.A free source-linked morning brief.
Start free briefUpdated August 21, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
Decision reading
Agents-A1 has the higher public score estimate, 61.25 versus 50.76, but the 90% score intervals overlap. Treat that as a lead, not a settled winner.
2 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.
Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.
Prompts that approach the documented context limit
Agents-A1
Agents-A1 has the larger documented context window.
Confidence: documented
Code generation, repair, and software-engineering tasks
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
Tool use, computer use, and multi-step task completion
Not enough matched evidence
The category averages use different weighted benchmark sets, so they are directional rather than like-for-like.
Confidence: limited
1K fresh input + 500 output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: rate-fallback
50K fresh input + 3K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
1 category uses different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Each row states whether both averages use the same weighted benchmark set. Directional and not-comparable rows remain visible, but they never receive a winner in this template.
| Category | Agents-A1 | Step 3.7 Flash | Weighted basis | Reading |
|---|---|---|---|---|
| Agentic | 75.5 | 66.4 | Directional only1 vs 2 rows | Directional only |
| Coding | Not measured | 56.3 | Not comparable0 vs 1 rows | Not comparable |
| Reasoning | 60.2 | Not measured | Not comparable1 vs 0 rows | Not comparable |
| Knowledge | 47.6 | Not measured | Not comparable1 vs 0 rows | Not comparable |
| Math | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Multilingual | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Multimodal | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Instruction following | 94.8 | Not measured | Not comparable1 vs 0 rows | Not comparable |
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
Too few matched category axes support a radar. The ruled list below shows only shared benchmark results; positions use each benchmark’s normalized display scale when available.
BrowseComp
Agentic
Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.
1K fresh input + 500 output tokens
Agents-A1 has no comparable published API token rate.
50K fresh input + 3K output tokens
Agents-A1 has no comparable published API token rate.
200K cached + 20K fresh input + 10K output tokens
Step 3.7 Flash has no published cached-input rate, so cached tokens use its listed input rate. Agents-A1 has no comparable published API token rate.
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
Maximum documented context; output-token limits may be lower.
Agents-A1
262K
Step 3.7 Flash
256K
Agents-A1
Not sourced
Step 3.7 Flash
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Agents-A1
No comparable hosted API rate
Step 3.7 Flash
Not published
Agents-A1
Not sourced
Step 3.7 Flash
Not sourced
Agents-A1
Not sourced
Step 3.7 Flash
Not sourced
Agents-A1
Not sourced
Step 3.7 Flash
Not sourced
Agents-A1
Reasoning
Step 3.7 Flash
Reasoning
Agents-A1
Open Weight
Step 3.7 Flash
Open Weight
Agents-A1
Open Weight
Step 3.7 Flash
Open Weight
Agents-A1
2026-06-26
Step 3.7 Flash
2026-05-29
Run the same representative tasks against both endpoints before changing production traffic.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
BrowseComp
Step 3.7 Flash leads this result
HLE w/ tools
Agents-A1 leads this result
VITA-Bench
Not directly comparable
Terminal-Bench 2.0
Not directly comparable
DeepSearchQA
Not directly comparable
Toolathlon
Not directly comparable
Claw-Eval
Not directly comparable
Gert Labs
Not directly comparable
LongBench v2
Not directly comparable
HLE
Not directly comparable
IFEval
Not directly comparable
Agents-A1 has the higher public score estimate, 61.25 versus 50.76, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.
The published evidence does not provide a shared weighted coding basis for both models, so BenchLM does not name a coding winner.
The current agentic tasks averages use different weighted benchmark sets, so BenchLM does not name a winner from them. Read the shared benchmark rows directly and test the models on the same task set.
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
Agents-A1 has the larger documented context window: 262K, compared with 256K.
Last updated August 21, 2026
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.