Machine Payment Gateway

Yoofooz Agent Pay

A non-custodial x402 gateway that lets autonomous agents discover a priced API, receive HTTP 402 payment requirements, pay the provider directly, and execute the API.

How it works

Agent → Yoofooz → 402 → payment authorization → verify → API execution → settle → receipt.

  • Providers register a public upstream API route.
  • Each route declares an x402 price, network, asset, and provider wallet.
  • The provider remains the direct payment recipient.
  • Yoofooz meters its platform fee as receivable revenue; it does not custody provider funds in the MVP.

MVP status

  • Gateway: Public testnet facilitator fallback enabled
  • Facilitator: Reachable — x402 v2 exact supported on Base Sepolia
  • Testnet pilot: Ready for signed test payment
  • Network lock: eip155:84532
  • Providers: 1
  • Routes: 1
  • Settled transactions recorded: 0
  • Platform-fee model: metered receivable / invoiced separately
  • Custody: provider-direct

Public Agent Pay routes

Agents can use the machine-readable catalog to inspect price and x402 payment requirements before calling a route.

ProviderRouteMethodPriceNetworkGateway URL
Yoofooz TestnetAgent Pay EchoPOST$0.01 test USDCeip155:84532https://yoofooz.com/agent-pay/yoofooz_testnet/echo

Provider economics

The x402 payment requirement sends funds directly to the provider's configured wallet. Yoofooz records its configured basis-point fee against successful settlements for later invoicing. This keeps the MVP non-custodial while creating transaction-based platform revenue.