The agent economy: how MCP and x402 work together

Before MCP, connecting a model to an external capability meant a bespoke integration per pair: this agent framework to that API, again and again. MCP replaced that with a universal socket — a server describes its tools in a standard schema, any compliant client can list and call them, and transports cover both local processes (stdio) and remote services (Streamable HTTP).

What MCP deliberately doesn't address is money. The protocol assumes access is either free or sorted out-of-band with keys and OAuth. That works for a developer wiring up their own tools; it fails for an open market, because the people running good servers have hosting bills and upstream costs, and 'free forever, maintained by goodwill' is not infrastructure.

x402 made HTTP itself payable. A service responds 402 Payment Required with a machine-readable price; the caller pays in USDC, settlement clears on Base in about two seconds, and the retried request executes. No account, no invoice, no card form — and the $0.01 minimum makes single-call purchases economically sane, where card rails would drown them in fees.

What x402 alone lacks is a storefront. A payable endpoint is just a URL; nothing in the protocol tells an agent that the endpoint exists, what it does, or whether the price is competitive. Payment rails without discovery is a shop with no street.

Put them together and a complete transaction becomes possible with no human in it. An agent queries an index for a capability — say, parsing a filing or geocoding an address. It gets back an MCP server's URL, tool schemas, and per-call price. It connects, calls the tool, receives the 402, pays from its wallet, and the payment settles before the handler runs. The result comes back with an Ed25519-signed receipt; the agent's operator gets a verifiable record of what was bought and for how much.

Notice the division of labor: MCP carries the what (tools, schemas, invocation), x402 carries the how much (price, payment, settlement). Neither protocol had to grow features outside its lane.

Agents transact at a frequency and anonymity that human billing infrastructure was never built for. Per-call USDC payment means no credit relationship needs to exist before the first call. Two-second settlement means the purchase fits inside an agent's working loop. No chargebacks means a seller can serve ten thousand anonymous callers without fraud-ops headcount. And signed receipts mean the whole history is auditable after the fact — which is what lets operators give agents budgets and trust the accounting.

Loomal is the index layer: a machine-queryable catalog where every listed MCP server and API endpoint carries its price and payment endpoint alongside its tool list, so the discovery step and the payment step use the same record. For builders, that's the practical on-ramp to the agent economy — list a server, set a per-call price from $0.01, and the fee is 5% on settled transactions, currently waived.

If you're starting today: build or claim your MCP server, gate the expensive tools with x402, and list it. The loop described above then runs without you in it — which is the point.