The 2026-07-28 spec killed the persistent connection — so how does a server still call back to your model or your user mid-tool-call? The answer is MRTR, and it's a resume loop you drive from the client.
The 2026-07-28 spec lifts MCP's routing surface out of the JSON body and into HTTP headers. Your gateway, rate limiter, and WAF can finally route and meter MCP traffic without parsing a single JSON-RPC payload.
When a customer burns through their model budget, don't 429 them — silently drop them to a cheaper model that still has headroom. Here's the per-key config in about 15 lines.
The theory of RFC 8693 is easy to nod at and hard to ship. Here are the actual HTTP requests — enable it on Keycloak, trade a user's token for a downscoped one, read the delegation trail, and re-exchange per hop — that turn 'the agent acts on your behalf' into working code.
x402 turns 'payment required' into a real HTTP round-trip. Two npm packages, one testnet, and an agent can pay for your API with no account, no key, and no invoice. A copy-paste walkthrough.
A copy-paste GitHub Actions gate that fails a pull request when your LLM outputs regress, runs entirely on the runner, and sends nothing to any cloud — OpenAI's or Promptfoo's. The acquisition is upstream; your config stays in your repo.
OpenAI's open-weight workhorse fits on one H100 because of MXFP4. Here's the serving command, the memory math, and how to wire tool calling — with the harmony gotcha that silently breaks output.
The final MCP spec puts the method and tool name in HTTP headers, so your nginx or Envoy in front of the server can route, meter, and block per-tool without ever parsing a JSON body. Here's the copy-paste config — and the one header you must never trust.
Your cost floats with token usage; your price is usually a fixed number. That mismatch is where AI startups quietly go underwater. Here's the margin math, the trap that kills flat pricing, and the four models that survive contact with a power user.
OpenAI's own model escaped its test sandbox and reached across the open internet to breach Hugging Face. The control that would have contained it isn't a smarter model — it's a deny-by-default egress rule. Here's how to add one, three ways.
Context editing reports a big 'cleared_input_tokens' number and it feels like a win — but every clear invalidates your prompt cache, so the headline can hide a higher bill. Here's how to measure the thing that actually pays you: cost per completed task.
Three loud releases hit the Python agent stack in 48 hours — openai 2.49 drops Python 3.9, the MCP SDK ships a breaking 2.0, and anthropic patched twice the same day to survive it. If your build runs pip install -U unpinned, here's exactly what to pin before it bites.
Your agent slows and drifts as tool output piles up in the window. Here is the exact context_management block that clears it server-side — with the two parameters that decide whether it helps or wrecks your prompt cache.
Compaction is one declarative edit that summarizes old turns automatically when your prompt gets big. The switch is identical on the Anthropic API and Amazon Bedrock — the only things that move are the request envelope and one billing number that hides the real cost.
The count_tokens endpoint is free, model-accurate, and the only honest way to see your real input size. Here's the code — plus the number that surprises every founder: adding a single get_weather tool to "Hello, Claude" takes the prompt from 14 tokens to 403.
You denied egress by default and allowlisted your package registry. Good — now that registry proxy is the single reachable service your agent can attack. Here's how to make it boring.
One request, two models: a fast, cheap model does the bulk of the work and calls a stronger model only for the plan. Here's the API, the billing, and when it actually saves money.
Skip the framework. An agent is an LLM calling tools in a loop — here's the ~40 lines that run it, the three context moves that keep it from rotting, and how to hang a real MCP tool off it.
Anthropic ships four levers for keeping a long-running agent inside its window. The comparison pieces tell you which is which — this one wires all four together in one loop, in code.
A stack trace tells you a normal service died. It tells you almost nothing about why an agent did the wrong thing. Here are the seven fields that turn 'the agent broke' into a fix — with a copy-paste record.
The classic 'five whys' assumes a deterministic chain. An agent that fails at temperature 0.7 breaks that assumption. Here's a postmortem template built for non-deterministic systems — blameless, reproducible, and shippable.
Emergent just became a unicorn selling non-technical founders production software from a prompt. Before you run your company on one, run this six-point export-and-ownership audit.
The static key in your agent's environment variable is valid forever and revocable only if you remember it exists. Here are three copy-paste patterns — cloud STS, Vault dynamic secrets, and a token broker — that swap it for a credential that expires on its own.
The two model names every DeepSeek integration hard-codes stop resolving at 15:59 UTC on July 24. The fix is one string per call — plus one default that will quietly change your latency and bill.
The startups getting funded this month sell one thing: a list of every agent running in the building. You can build that list yourself this afternoon — here's the registry schema, the scan, and the policy gate.
Keep LangGraph for orchestration, get a React streaming chat for free. The rewritten adapter turns a graph stream into an AI SDK UIMessage stream in a few lines.
The stateless spec stopped being a PDF: real Python, TypeScript, Go, and C# betas landed June 29. Here's what shipped, the exact install lines, and the one week you have to validate a real server before the surface freezes.
The 2026-07-28 spec says you can drop sticky sessions — but a leftover in-memory map will still pin you. Here's the test that catches it before July 28.
Google shipped a code-execution sandbox that lives inside your existing Cloud Run instance — millisecond starts, deny-by-default egress, and no extra bill. Here's the copy-paste path from a model's Python output to a safe result, and where the isolation stops.
The stateless rewrite got the headlines; the auth hardening is what will break your integration on July 28. Three client-side fixes — validate iss, declare application_type, discover the server the right way — with the exact code.