A few months ago, I got tired of manually checking which AI model had the longest context window. Every week, some provider would quietly update a model card, or a new release would drop with a bigger number, and the leaderboard would shift without anyone noticing.

So I built something simple but obsessive: an automatically updating database that scrapes and ranks 360+ AI models by their advertised context windows(https://modelatlas.net/blog/long-context-models) or pricing (https://modelatlas.net/blog/cheapest-ai-models). It pulls from OpenRouter, official provider docs, and model cards. Every time a provider changes a spec, the database updates within hours.

Then, when I was watching it, the ranking algorithm did something that made me stop everything.

Llama 4 Scout appeared at the #1 position with a context window of 10,000,000 tokens.

I stared at the number for a solid minute. Ten million. That wasn’t just bigger than GPT-4. That was bigger than Claude, bigger than Gemini, bigger than everything. 5 Times the Second Largest (Grok after Llama’s claims). My first thought was exactly what you’d expect: "... What?"

I had to dig in.

The Hype: What Meta Is Actually Selling

Let's put 10 million tokens in perspective. That's roughly 7.5 million words. You could fit the entire Harry Potter series into a single prompt and still have room for follow-up questions. You could dump a decade of customer support tickets, a full corporate legal discovery, or a massive codebase with full commit history — all at once.

Meta’s strategy here is pretty brilliant. While OpenAI, Anthropic, and Google are gatekeeping long-context behind enterprise tiers and 20+/month subscriptions, Meta went the opposite direction: they tried to make context length a commodity, not a luxury feature.

Llama 4 Scout is built on a Mixture-of-Experts (MoE) architecture: 109 billion total parameters, but only 17 billion active per token. This keeps inference costs manageable. The real magic, though, is iRoPE — interleaved Rotary Position Embeddings. Meta alternates between standard RoPE layers (which handle local context) and NoPE layers (No Positional Encoding, which attend globally without distance bias). This 3:1 pattern is how they claim to scale to 10M without the quadratic memory death spiral that kills most models past 128K.

The pricing is almost absurdly cheap: 0.08 per million input tokens on OpenRouter. For an open-weight, natively multimodal model that can theoretically ingest 10M tokens at once.

On paper, Meta just made every proprietary long-context model look overpriced and underspecced.

The Truth: Where the Numbers Start to Lie

Here's where I have to be transparent, because I actually tested this and the marketing doesn't survive contact with reality.

First, the OpenRouter reality. Scout's architecture supports 10M tokens. But on OpenRouter, it's currently hard-capped at 327,680 tokens. That's still massive — larger than most production workloads need — but it's not 10M. No hosted provider is serving the full window yet. The 10M number is a theoretical ceiling, not a practical one.

Second, context window ≠ comprehension window. This is the part that stings. Independent benchmarks from Fiction.LiveBench show Scout achieving only 15.6% accuracy on tasks requiring understanding within a 128K context window. That's not a typo. At 128K — a fraction of its claimed capacity — it's struggling significantly. Needle-in-haystack retrieval works fine; it can find a specific fact buried at token 9,000,000. But ask it to reason about that fact in relation to something at token 1,000,000? It hallucinates, forgets, or fixates on recent tokens.

The effective reasoning cutoff seems to land somewhere around 256K tokens. Beyond that, you're not getting a reasoning partner; you're getting a very expensive search index with a language model attached.

Third, the competition caught up — and surpassed it. While Scout was grabbing headlines with 10M, DeepSeek quietly shipped V4 with a 1M-token context window that's actually usable. DeepSeek V4-Pro handles 1M tokens with hybrid sparse attention, uses only 27% of the inference FLOPs compared to its predecessor, and costs 0.435 per million input tokens. DeepSeek V4-Flash is even cheaper at 0.14 per million. And unlike Scout's theoretical 10M, DeepSeek's 1M is the default across all official services, with benchmark scores that actually hold up at scale.

Even Grok offers a 2M context window — the second largest after Scout's claimed 10M — and while it's behind xAI's tiered API, it's at least a real, served number.

So no, Scout is not the "best value long-context model on OpenRouter right now." DeepSeek V4 exists. Grok exists. Scout is cheap, but cheap doesn't automatically mean best value if the comprehension doesn't scale with the window.

Why I Still Think the Discovery Matters

If Scout is flawed, why am I writing about it?

Because this is exactly why I built the auto-updating database. The AI landscape is now so noisy that a model can claim a 10M context window, get buried under a dozen other announcements, and most developers will never know it exists — let alone know that the real cap is 327K and the real comprehension drops off at 256K.

I found Scout because my database doesn't read press releases. It reads numbers. And those numbers told a story: Meta is making a bet that context length will be democratized through open weights, even if the execution isn't there yet. They're selling the possibility of 10M tokens, and eventually, someone will build the infrastructure to serve it.

That's the real narrative. Not "Scout is amazing." Not "Scout is trash." But: the context window wars are moving so fast that you need a living database to track what's real and what's marketing.

The Tool I Built to Navigate This Chaos

This is where I'll be direct with you.

I built https://modelatlas.net because I got tired of opening five different tabs to compare models. It’s a unified dashboard and chat interface for 360+ AI models, built on top of OpenRouter. You bring your own API key — free to create — and you can chat with any model in the catalog instantly, without managing separate accounts or subscriptions.

The context window rankings that found Scout? That's live on the site. Updated automatically. You can see which models actually serve their advertised context, which ones are capped by providers, and which ones deliver real comprehension at scale.

Want to stress-test Scout’s 327K limit yourself? You can https://modelatlas.net/chat. No setup beyond pasting an OpenRouter key. There’s a full tutorial in-site if you’ve never generated one before — takes about 30 seconds.

Want to see how it actually compares to DeepSeek V4 or Grok on the same prompt? Switch models mid-conversation. The whole point is removing the friction between "I heard about this model" and "I'm actually testing this model."

• https://modelatlas.net/find-ai
• https://modelatlas.net/model/meta-llama-4-scout
• https://modelatlas.net/chat

The Bottom Line

Meta's strategy with Llama 4 Scout is clear: democratize the context window itself. They want to be the company that made 10M tokens an open-weight reality, even if the current implementation is more aspirational than actual. The iRoPE architecture is genuinely interesting. The MoE efficiency is real. The 327K served window is still useful for plenty of RAG and retrieval tasks.

But the gap between "architecture supports 10M" and "model comprehends at 10M" is massive. And in that gap, models like DeepSeek V4 are eating Scout's lunch with smaller advertised numbers that actually work.

The AI space doesn't need more hype. It needs more transparency. That's why I built the auto-ranking database. That's why I built ModelAtlas. And that's why I'm telling you about Scout — not because it's the best model, but because finding it, testing it, and understanding its real limits is exactly what we should all be doing.

Have you pushed any long-context model past 200K tokens in production? Where did it actually break? I’d genuinely love to know.