Sumdaysumday.dev

Every way an agent can pay, in one connection.

Tell your agent what you want and let it pay. Which provider reaches which merchant, which combinations hold together, what each one unlocks — keeping that straight is our job. Yours is one sentence.

17 providers wired up1,271 paid endpoints in the MPP registry
Every claim on this site is graded and dated. How we grade →
route tracetrace 01 / 02
> “Book me a flight to Lisbon under $600.”
reachExpedia MCP — finds and holds the itinerary✓
railPurch — Amazon and Shopify only✗
railconnected wallet — pays the fare✓
limitCrossmint — caps the charge at the fare✓
routeExpedia MCP + wallet + Crossmint cap→
The router’s actual job: which rail reaches this merchant, at this amount, under the limits you set. A rejected rail is part of the answer.

One connection. The routing is the product.

01 · the map

Not another payment rail — the router between them. Your agent gets one set of tools; behind it, 17 providers answer five different questions. Swapping the rail underneath a purchase never means rewriting the agent.

your agentone sentenceSumdayreach · amount · limitswhat shops7 providers · finds + holdswhat pays6 providers · moves moneywhat vaults1 provider · user-ownedwho drives1 provider · decides to spendwhat proves the agent2 providers · identity

No single rail reaches everything

02 · coverage, as checked 3 Aug 2026

MPP reaches 141 services. x402 on Base reaches a different set. Purch reaches Amazon and Shopify. Stripe Link is a card on file for Directory merchants. No standard spans them — the union does.

AmazonShopify storesStripe merchantspaid APIsmarkets (USDC)person-to-person
Purch
Stripe Link
MPP
x402 · USDC
One Sumday connection
reaches ita different subset eachno pathrouted through the one connection

Swap the rail. Keep the agent.

03 · the contract
the agent’s side — never changes
tool pay(merchant, amount, limits)
tool can_reach(merchant)
tool receipt(payment_id)

The agent holds three tools and a budget. Everything below this line is Sumday’s problem.

the rail underneath — swaps per purchase
route →
Stripe Link
card on file → Directory merchant → settled

Same three tools, four different rails, four different receipts. The agent’s code hasn’t moved.

0
providers wired up today
0
services in the MPP registry
0
paid endpoints in that registry
0
published findings, graded and dated
This page is the map. The results have their own pages.

Which provider is live, in part, or gated upstream — and what we found when we ran each one. Every claim graded and dated.

The providers →The findings →
The connection isn’t open yet. Get it when it is.

We’re still building the router behind all this. Tell us what you want your agent to pay for and it shapes what we wire up first.