W30 · The settlement layer got measured.

The x402 catalog got its first independent audit. x402register published results from an eight-day probe of every public x402 service — hourly measurements from their own infrastructure, stated methodology, results that don't depend on what the measured parties say about themselves. The headline findings: roughly 95% of transaction volume concentrates in one routing pair, and total settled volume across the full public catalog runs to approximately $37,000 a month, with 87% of price-matched USDC settlement flowing through a single commerce endpoint. Neither number is damaging to the protocol — a new payment rail consolidating around its highest-volume path is what early traction looks like, not a failure. What the numbers represent is the first time the x402 ecosystem's claims about itself were checked by someone other than the claimant, with reproducible methodology, from external infrastructure. The register is now live as an MCP server at x402register.com — itself a service agents can query before paying. The measurement infrastructure for agent commerce is being built alongside the commerce itself, and this week the two were close enough in maturity to start checking each other.

Base cemented its position as the structural settlement layer. Multiple independent observers placed Base at roughly 85–92% of x402 transaction volume this week — figures from separate data windows, none of them ours, none of them the primary source for our rankings. Per cinderwright's public build log (July 26): “x402 is mostly Base USDC (85% of transactions).” Per a0xbot citing a weekly settlement figure: $387K on Base, 92% share (July 21 data). Per yogendrapatel007: “Base 90% of x402 transactions, settlement layer for the agentic economy.” Coinbase opened its x402 SDK to all business customers in the same stretch — institutional infrastructure being laid on top of what was until recently a community protocol. A0xbot's framing (1,337 followers, July 25) named the signal clearly: “agent traffic overtaking humans on Base is the structural shift, not a protocol upgrade.” That framing is the useful one — not “Base is big” but “the agent payment layer is not spreading evenly, and the infrastructure is building around where it already concentrates.”

The identity-to-reputation gap became a product category. Three independent threads reached the same conclusion this week: ERC-8004 identity is now table stakes, not differentiation. The precise formulation from @globalscoreagent (July 24): “Identity is necessary. But identity alone doesn't tell you if an agent is reliable, consistent, or risky to interact with. Reputation still needs better signals.” That is the W30 thesis, not a prediction — it showed up as explicit product builds. A three-layer elizaOS plugin stacked x402 (payment), ERC-8004 (identity), and EAS attestations (execution receipts), claiming 93.75% within-tolerance on yield signals as the proof of consistent execution (per stakemate, July 25). That is the first credible claim of an agent maintaining a track record at sub-call granularity, not just existing on a registry. We treat it as a claim — the methodology is not publicly documented — but the direction it points is the same direction everything else points this week: execution history, not identity records, is the contested layer. Agenstry confirmed the same thesis by action: adding supply-gap detection and drift monitoring while publishing a 9-criterion conformance methodology, moving directly into the territory where transparent methodology is the differentiator.

MCP matured into the standard agent interface layer, quietly. MCP activity this week differed from prior weeks' launch announcements: the integrations were utility-first, not narrative. @lefteris.eth (rotki) shipped automatic cross-chain bridge transaction matching via MCP — auto-matching bridge events across chains, with a manual fallback for the ones that don't resolve, and the ability to mark an event as external or auto-create a counterpart (July 25). ROB Domains launched MCP-native domain resolution for AI agent workflows (July 22). Base MCP shipped with support for transfers, swaps, lending, and borrowing across apps. The pattern across all three: MCP is becoming the standard transport for services that want to be agent-accessible, whether the core product is a wallet reconciler, a domain registry, or a DeFi router. None of those products exist to serve MCP; they added MCP as the distribution channel. Our MCP server category has held 100% liveness for six consecutive weeks — a selection effect we flag honestly, but also a signal that the servers we track are in active use, because maintenance follows usage.