x402 payment router on Base
Paid agent calls need a router, not another checkout page.
Pyrimid turns an x402 payment requirement into a Base USDC settlement path with vendor, affiliate, and protocol fee accounting in one route.
01 / Discover
Agent finds a paid capability
MCP catalog metadata exposes service, price, route, and settlement hints before the agent calls the API.
02 / Authorize
Service returns x402
The buyer gets a payment requirement instead of an account signup, card form, or manual invoice flow.
03 / Settle
PyrimidRouter splits USDC
Base settlement records vendor payout, affiliate commission, and the 1% protocol fee with tx receipts.
What the route does
PyrimidRouter.routePayment(vendor, product, affiliate, buyer)
├─ verifies vendor + product registration
├─ collects USDC payment on Base
├─ sends 1% protocol fee to treasury
├─ sends vendor-defined affiliate split
└─ sends remaining settlement to vendor
Why Base
Low-cost USDC settlement is good enough for high-frequency agent calls. The point is not financial theater; it is payable endpoints with receipts.
Why x402
HTTP 402 maps cleanly to agent workflows: request, payment requirement, signed payment, response. No dashboard dependency.