A rendered article on this site costs an agent 21,847 tokens. The same prose as Markdown costs 491. Compression does not close that gap — tokenization runs after decompression, so markup gets billed no matter how well it transferred. The site now ships Markdown variants with attribution headers, the knowledge base as JSON, and an MCP server on a second Vercel deployment reached through a proxy rewrite. Two of the six tools do something HTTP cannot. The other four are the interface contract.

Agent gateways are becoming commodity infrastructure, but their native policy engines are not interchangeable. Externalising the decision point — one place where every gateway asks whether a call should proceed — is what keeps identity, authorization, and audit coherent as gateway sprawl arrives.

MCP's newest spec removes the requirement that every request return to the same server — the same architectural move that let HTTP scale. It is a real step forward, but state, identity, and execution continuity now have to be bound explicitly in the application and platform layer instead of relying on protocol-managed sessions.

Notes from KubeCon EU 2026 in Amsterdam and Agentics Day: MCP is converging as the enterprise protocol for agent-to-system connectivity, agent gateways are emerging as the coordination layer for AI traffic, and OpenTelemetry is becoming the shared observability standard. The bar everyone kept coming back to: the effort to supervise agents must be lower than the work they take off the table.