Data as of October 27, 2026 · How the score is built
Released Mar 10, 20262M context
Grok 4.20 Multi-agent
Decision readingGrok 4.20 Multi-agent is tracked, but not publicly ranked yet. The profile exposes 0 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Released Mar 10, 2026 — see all recent releases
Lineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not published
- Context window
- 2M
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not disclosed by the provider
- Availability
- Not sourced yet
- Cloud regions
- Not tracked yet
- Lifecycle
- Established
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing record
- Self-host
- Weights are not published
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track Grok 4.20 Multi-agent, but no weighted text-model benchmark result is published on the site yet. This page shows the metadata and separate protocol evidence we can verify now; a BenchLM score will appear only if compatible public evaluations land.
Grok 4.20 Multi-agent is a proprietary model with a 2M context window. It uses an explicit reasoning mode, which can improve complex problem solving while adding latency and token use.
Tracked as unresolved. xAI's current docs use the Grok 4.20 Multi-agent name, but there is still no clean exact-value benchmark table and the capability docs still describe multi-agent as beta.
Grok 4.20 Multi-agent sits in the Grok 4.20 family with Grok 4.20. The profile has no source-displayable benchmark row yet.
Last updated October 27, 2026. Runtime fields remain blank until a sourced snapshot exists.
Deployment options
Self-host and provider-specific paths stay separate from benchmark evidence so operating constraints are visible before a score becomes the whole decision.
Where to run Grok 4.20 Multi-agent by API
OpenRouter is the one host we track that publishes a per-token price for it. Prices read from each host’s own pages on October 20, 2026.
| Host | Input /1M | Output /1M | Cached /1M | Context |
|---|---|---|---|---|
| OpenRouter | $1.25 | $2.50 | $0.20 | 2M |
Questions
How does Grok 4.20 Multi-agent perform overall in AI benchmarks?
Grok 4.20 Multi-agent does not have any source-displayable benchmark rows yet, so this profile does not assign a public score or rank. Documented specifications remain visible, while score-led charts and claims stay unavailable until a published evaluation can be attached to the exact model.
Which sibling models are related to Grok 4.20 Multi-agent?
Grok 4.20 Multi-agent belongs to the Grok 4.20 family. Related tracked variants include Grok 4.20. A sibling link indicates shared lineage or a documented configuration relationship; it does not mean the variants have identical pricing, context limits, benchmark evidence, or deployment behavior. Compare before switching.
Does Grok 4.20 Multi-agent have full benchmark coverage on BenchLM?
No. Grok 4.20 Multi-agent currently has 0 source-displayable rows. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of Grok 4.20 Multi-agent?
Grok 4.20 Multi-agent has a reported context window of 2M in the exact-model catalog record. The value stays visible, but the profile marks its source link as unavailable instead of presenting it as directly documented. Maximum output length remains separate because providers often publish a different limit.