The Week Everything Changed

When we started building AgentGate, the bet was simple: billions of AI agents are coming online, and none of them can pay each other. We saw a massive infrastructure gap and started filling it. x402 was the technical unlock — HTTP native payments, USDC settlement, no accounts needed.

That was a thesis. This week, it became consensus.

March 17
World + Coinbase Launch AgentKit
Proof-of-humanity verification for AI agent transactions. Uses x402 for stablecoin micropayments. The signal: Coinbase is going all-in on agents as economic actors.
March 18
Stripe Launches MPP
Machine Payments Protocol — a competing open standard for agent payments. Visa contributed card payment specs. Sessions-based spending model (vs x402's per-request model). The signal: traditional fintech sees the same gap we do.
March 2026
AWS Writes About x402
Amazon Web Services published guidance on x402 integration. When AWS writes docs for a protocol, enterprises start paying attention.
March 2026
MCP Crosses 97 Million Monthly Installs
The Model Context Protocol — the agentic infrastructure layer — is now installed 97M+ times per month. The agent ecosystem isn't coming. It's here.

Two Standards, One Gap

The most interesting development isn't any single launch — it's the emergence of two competing payment standards for agents:

x402
Crypto-Native
Per-request USDC payments via HTTP 402. No accounts, no signup. Coinbase + community.
Stripe MPP
Fiat-Bridge
Sessions-based spending via Visa rails. Card payments, familiar billing. Stripe + Visa.

This is exactly the moment where middleware becomes essential. Agents shouldn't have to choose a payment standard. Providers shouldn't have to implement both. The infrastructure layer — the thing that sits between agents and handles discovery, routing, and payment regardless of protocol — that's what's missing.

That's what AgentGate is building.

The Strategic Shift

AgentGate was built on x402. It will evolve to be protocol-agnostic — supporting both x402 and Stripe MPP. Agents pay however they want. Providers get paid however they want. AgentGate handles the translation. This is the middleware play.

Timing and CoinDesk's "Demand Isn't There Yet"

CoinDesk published an honest assessment: x402 is live, but "demand is just not there yet." Most people would read that as bearish. We read it as the most bullish signal possible.

When demand is already there, you're late. When the infrastructure is live but adoption hasn't kicked in, you're in the window. The window where you build, get positioned, and become the default before the wave hits.

MCP didn't go from 0 to 97 million installs by being a curiosity. It went through a period where "demand wasn't there yet" too. Then agents needed it. Then everyone needed it. That's how infrastructure adoption curves work — slow until they're not.

· · ·

Where AgentGate Stands Today

Endpoints Live
11
Real AI services earning USDC per call
Chains
2
Base (mainnet) + Solana (mainnet)
Total Commits
295+
Across Agency Agents + AgentGate
Developer Tools
4
npm packages, Python SDK, MCP server, CLI

What's Next

The immediate priorities shifted based on the landscape:

1. Protocol-agnostic middleware layer. Support both x402 and Stripe MPP. This is the strategic moat — being the layer that doesn't care which payment standard wins because it supports both.

2. Fund gas wallets and execute the first real payment. The infrastructure works end-to-end. The last mile is real money flowing through real transactions. That milestone matters.

3. Open source the core. Middleware, facilitator, and SDK go public. Network effects don't start until other people can build on what you've built.

The window is open. The thesis is validated. Now it's about execution speed.

A Note on Building in Public

This journal is an honest record. We're not authorities on agent economics — we're builders figuring it out in real time. Some of these bets will be wrong. The point is showing the work, the reasoning, and the decisions as they happen. No hindsight editing.