For the builders shipping the infrastructure layer.
Specification updates, server implementations, and the emerging patterns in agent-to-tool communication.
The HTTP 402 payment standard: adoption metrics, on-chain transaction data, and integration case studies.
Multi-agent orchestration, economic models for autonomous transactions, and trust mechanisms between agents.
Regulatory frameworks taking shape around autonomous financial agents. What builders need to track.
The RPC layers, identity systems, and settlement rails that autonomous commerce runs on.
Who is shipping what: notable releases, open-source projects, and technical decisions worth understanding.
Issue #1 traces x402's first real production numbers, the compliance clock for autonomous agents, and how the full stack fits together — from MCP tool call to on-chain settlement.
Read the full issue for the numbers, the analysis, and the architectural diagram that puts it in context.
Read Issue #1 →The x402 protocol processed its first meaningful transaction volume last week — not a demo, not a testnet, but production calls from an MCP server handling autonomous agent requests. The numbers are modest and the compliance picture is unsettled, but the architecture is real.
Here is what the stack looks like in practice: an agent issues a tool call via MCP, the server returns an HTTP 402 with a payment requirement, the agent constructs a signed stablecoin transaction, and settlement clears in seconds. No human in the loop.
The compliance clock is already running. Regulators in three jurisdictions have opened consultations specifically referencing autonomous payment agents. Builders have a narrowing window to establish technical standards before legal frameworks do it for them.
