Tutorials, comparisons and design patterns for building autonomous agents that self-fund, call 345+ models and orchestrate MCP Tools.
Visa's Trusted Agent Protocol puts a cryptographic signature on every agent request that touches a merchant site, so the merchant can tell an accountable agent from an anonymous bot. No money moves over TAP. We walk the RFC 9421 headers, the agent-browser-auth and agent-payer-auth tags, the Consumer Recognition Object, the three payment containers including the HTTP 402 IOU, and an audit of the reference implementation that has not been touched since October 2025.
Four things happened between July 24 and July 31: the largest MCP revision since launch went final, Hugging Face published a 17,600-action forensic timeline in which commercial models refused to help the defenders, NVIDIA assembled a security alliance around open models and agent identity, and x402 spent the week fixing the unglamorous parts of its HTTP semantics.
MCP's 2026-07-28 revision did two things at once: it rewired every server-to-client request through Multi Round-Trip Requests (SEP-2322), and it deprecated three of them — roots, sampling and logging (SEP-2577). We walk the MRTR wire format, the cryptographic rules on requestState, the ephemeral-versus-Tasks split, and why the official migration path for sampling — 'integrate directly with LLM provider APIs' — changes who pays for inference.
MCP Apps (SEP-1865) is the first official MCP extension and, as of the 2026-07-28 spec, one of exactly two. We walk through the ui:// template scheme, the sandboxed iframe model, the JSON-RPC-over-postMessage bridge, the CSP MUSTs, and the new attack surface — then map it to an x402-billed gateway.
The 2026-07-28 spec tells agents how to talk to MCP servers — the official MCP Registry is how they find them. We dissect the whole machine: the server.json publication format and its 2025-12-11 schema, namespace verification via GitHub OAuth and DNS TXT records, package ownership validation with mcpName, the frozen v0.1 REST API with cursor pagination and updated_since sync, and the subregistry model where the root stays neutral and opinion lives downstream. Then we crawl the live API ourselves to measure what is actually registered, and place the registry against x402 Bazaar and ERC-8004 as the third discovery layer of the agentic stack.
The MCP spec that finalizes today demotes Tasks from experimental core feature to official extension — and redesigns it around statelessness. We dissect the new lifecycle: server-directed task creation via CreateTaskResult, the five-status state machine (working, input_required, completed, failed, cancelled), idempotent tasks/get polling, keyed inputRequests for mid-task elicitation, cooperative cancellation, TTL semantics, and the identity gap where a taskId becomes a bearer token. Then: what a durable task rail means for a gateway that bills agents per call.
The stable Enterprise-Managed Authorization extension makes the corporate IdP the decision-maker for MCP access: an ID token is exchanged for an ID-JAG (RFC 8693), which is redeemed for an access token (RFC 7523) — no browser redirect, no per-server consent. We walk both legs of the flow, the ID-JAG claims and validation rules, the adoption map (Okta, Claude, VS Code, Linear, Atlassian), and where the identity rail meets the x402 payment rail.
Long-lived agents produce artifacts — video masters, dubbed audio, datasets — and most of them have no disk. The usual fix is pasting cloud credentials into prompts, which is an anti-pattern with a blast radius. This post opens up the Agent Workspace: inline uploads under 10 MB, single-use presigned R2 PUT URLs for everything bigger, downloads always proxied through the worker so per-GB billing is enforceable, retention with automatic expiry. Then we run the projection for our own autonomous video factory — one documentary a day, three dub tracks, up to 16 localized shorts — at the published rates: ~91 GB archived in year one for roughly $25-29, about 0.8% of what generating those videos costs. Plus the honest comparison with S3, where storage looks cheaper until egress bills you $0.09/GB every time the catalog leaves the building.