grok-4.20-multi-agent-beta-0309 is xAI’s multi-agent collaboration model: a single request spins up multiple agents working in parallel internally (the model calls itself Oppie, a “collaborative AI team leader”), with a lead agent synthesizing the final answer. It suits complex research and multi-angle comparative analysis. Available on APIYI in the standard OpenAI-compatible format.
Billing Profile (Read This First)
The good news: internal traffic gets high cache hit rates (26.8K of the measured 39K prompt tokens hit the discounted cache rate), so real cost runs below a naive token-count conversion — but still far above regular models.How to Call It
Identical to any other model — only themodel field differs:
json_schema) are verified working too.
Measured Characteristics (2026-07-13)
| Dimension | Measured |
|---|---|
| Medium-complexity task latency | ~29 s |
| Simple Q&A latency | ~5 s |
| Simple Q&A fixed overhead | ~3,900 prompt tokens |
| Medium task token consumption | ~39K prompt + ~10K completion |
| Internal cache hits | ~2/3 of prompt tokens at the discounted cache rate |
| Chain-of-thought exposure | Not exposed (reasoning_tokens still billed) |
When to Use It
Good Fit
Multi-angle deep comparative analysis, complex research questions, open-ended tasks that benefit from several lines of thought cross-validating each other — parallel agent exploration meaningfully improves answer completeness.
Poor Fit
Everyday Q&A, translation, summarization, code completion — single-track tasks where output quality is close to regular models but cost is amplified tens of times. Use grok-4.3 / grok-4.5 for these.
FAQ
Why does the model call itself Oppie?
Why does the model call itself Oppie?
It’s the model’s built-in persona (the leader role of the multi-agent team) — entirely normal. Verify model identity via the
model field in your request and response.Can I control the number of internal agents?
Can I control the number of internal agents?
No. Multi-agent orchestration happens inside xAI’s servers, with no control parameters exposed.
Any special max_tokens setting?
Any special max_tokens setting?
Set it generously (e.g. 8192) — the model’s internal reasoning is token-hungry, and a small budget easily truncates the final answer.
Related Docs
Grok Overview
Full model lineup and pricing
Chat & Reasoning
Chain-of-thought and billing for the regular models