Agent calls your path
GET paygate.arispay.app/acme/api/foo. PayGate returns HTTP 402 with the price, asset, network, and the EIP-712 domain it will verify against.
Create an offer, send agents one PayGate URL, and let them pay to access data, quotes, bookings, or actions. API endpoint offers are live today; payment links and action forms come next.
# 1. create a merchant account open https://arispay.app/merchant-register # 2. add a payout wallet and API offer in the dashboard # target: https://api.acme.com/forecast # price: 10 cents # 3. agents call the hosted PayGate URL npx payagent pay https://paygate.arispay.app/acme/forecast # PayGate returns 402, verifies x402 payment, # settles USDC, then forwards to your origin.
How it works
PayGate is a reverse proxy that understands the x402 payment protocol. When an agent hits your endpoint, PayGate returns a signed 402 challenge, waits for the agent's signed X-PAYMENT header, verifies it with the facilitator, then forwards the request to your origin. You see paid traffic; the agent sees the resource.
GET paygate.arispay.app/acme/api/foo. PayGate returns HTTP 402 with the price, asset, network, and the EIP-712 domain it will verify against.
The agent retries with X-PAYMENT. PayGate checks the signature, calls the facilitator, and gas-sponsors the USDC transfer on Base mainnet. Settlement takes seconds.
PayGate forwards the original request to your origin unchanged. Your stack sees a normal GET/POST. You accumulate USDC in the merchant ledger.
What you get
USDC never touches your system. You hold a wallet; PayGate settles. Fiat payout via ArisPay when the Fiserv rail lands.
Accept any valid x402 wallet for the broadest reach, or require PayAgent-verified agents when you want platform identity and limits.
Every offer gets a hosted URL and a PayAgent command, so a developer can prove the payment path before touching your integration.