IsItAgentReady vs Code Llama 4 (70B & 400B)

“The MCP server integration is the killer feature — I ran it directly from Claude Code on three client sites and had actionable fixes within a minute. The robots.txt check alone is worth the trip: most sites are blocking AI crawlers without realizing it.”

“The primitive here is raw model weights you can actually run: no API wrapper, no rate limits, no vendor controlling your uptime. The DX bet Meta made is correct — drop weights on Hugging Face, let the ecosystem (vLLM, llama.cpp, Ollama) handle the serving layer. The moment of truth is spinning up a 70B quant locally or on a single A100, and that actually works without 12 env vars. The 400B is a different story — you're in multi-GPU territory fast — but the 70B is a genuine weekend-deployable primitive. The specific decision that earns the ship: function calling support baked in at the weight level means you're not duct-taping tool use on top after the fact.”

“The 36 checkpoints sound comprehensive but several are aspirational standards that haven't been widely adopted yet — like MCP endpoint detection and agentic commerce. You risk over-engineering your site for agent features that most users will never use in 2026.”

“Direct competitors are GPT-4.1, Claude Sonnet 3.7, and Qwen2.5-Coder — all of which have closed weights or commercial restrictions. The specific scenario where Code Llama 4 breaks is enterprise fine-tuning at 400B scale: most teams can't afford the compute to actually adapt it, so they'll run 70B quantized and wonder why it doesn't hit benchmark numbers. The HumanEval and SWE-bench claims need scrutiny — Meta authored the eval setup, and 'state-of-the-art' on benchmarks designed around pass@1 on clean problems doesn't map cleanly to real codebases with legacy debt and ambiguous specs. What saves this from a skip: the permissive license is real, the Hugging Face availability is real, and the 70B model gives teams genuine pricing leverage against OpenAI. Prediction: this wins by being the baseline every fine-tune starts from, not by being the best raw model.”

“This is the 2026 equivalent of Google's mobile-friendly test from 2015. Sites that fail that test eventually lost traffic — sites that fail agent-readiness checks will lose AI-driven discovery. IsItAgentReady is the early warning system before that penalty is enforced.”

“The thesis: by 2027, the majority of production code-generation inference runs on self-hosted open weights because closed API costs are structurally incompatible with the volume that agentic coding pipelines generate. Code Llama 4 is a direct bet on that trajectory, and the 70B/400B split is smart — it covers the 'runs on one node' use case and the 'we have a cluster' use case simultaneously. The second-order effect that matters most isn't cheaper completions — it's that fine-tuning on proprietary codebases becomes viable without shipping your IP to a third-party API. The trend line is the commoditization of inference hardware plus the normalization of multi-step coding agents; Code Llama 4 is on-time, not early. The future state where this is infrastructure: every mid-size engineering org runs a Code Llama 4 fine-tune on their own codebase as a first-class internal tool, same as they run their own CI.”

“The graded report with step-by-step fix workflows is genuinely well-designed — it's the kind of output you can hand directly to a developer or a client without translation. Clean, actionable, and free.”

“The buyer here isn't an individual — it's an engineering team with a cloud bill and a compliance department that doesn't want code leaving the perimeter. That's a real, funded budget: 'self-hosted AI' sits in infra, not experimental tooling. The moat question is where this gets complicated: Meta has no moat in the traditional sense, but the ecosystem lock-in comes from fine-tune artifacts and toolchain integrations that accumulate over time. The real business risk is that Meta releases Code Llama 5 in eight months and the 400B variant is immediately obsolete before most teams have even finished deploying it — the open-source cadence creates capability depreciation that's faster than enterprise adoption cycles. Still a ship because the pricing model — free weights, you pay for compute you'd be paying for anyway — is the only model that survives contact with a CFO asking why you're paying per-token for internal tooling.”