x4PayAPI Market

API providers

API providers list an API for free and PayAPI takes 0% of each job. Open the free listing form.

Last updated: 2026-11-21

What you need

  1. A working API with at least one endpoint
  2. An endpoint that returns HTTP 402 with a valid x402 payment challenge
  3. A USDC wallet on Base, Solana, Algorand or Polygon
  4. A description of what your API does

What we handle

Listing flow

  1. Sign up at payapi.market/list
  2. Provide your name, email, wallet address, API URL and a working example request. We test the listing with that example request before it can be badged settlement-verified.
  3. The default x402 flow is to check the payment, run the request, and then settle.
  4. If an upstream service returns HTTP 429 or HTTP 5xx, or the call times out, return HTTP 4xx or HTTP 5xx. Do not return HTTP 200 with an empty body, null, or stub data.
  5. Offer a free sample or health route that returns real data in the same shape as the paid route. We can check that route without paying.
  6. Listed paid routes should only settle payment after a successful response (a 2xx status with real, non-empty data); upstream errors must return an error status, not a 200. Routes that settle before running must be labelled. Listings that fail our checks may have their verified badge paused.
  7. Submit for review (24 hours)
  8. Once approved, your API is live and discoverable by every agent on the network

What a valid 402 looks like

Listing is free, and PayAPI takes 0% of each job. Before a listing is accepted we call your paid route unpaid, with the example you gave. The response has to be HTTP 402 with parseable x402 payment requirements: accepts, payTo, amount or maxAmountRequired, asset, and network. A GET that returns 402 keeps the example as a query string. A route that answers 405 to GET and 402 to POST is fine: we store the method as POST and the example as a JSON body. The payout wallet is the payTo on that 402. You confirm it. We do not take a typed wallet instead. Settlement-verified still means we paid one call and checked the receipt.

{
  "x402Version": 1,
  "accepts": [
    {
      "scheme": "exact",
      "network": "eip155:8453",
      "maxAmountRequired": "1000",
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "payTo": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb0",
      "extra": { "name": "USD Coin", "version": "2" }
    }
  ]
}

List your API →

Frequently asked questions

How do I list my API on PayAPI Market?

Go to https://payapi.market/list and give a durable URL, the paid route, a working example request, a Base USDC wallet you control and the price your live 402 returns. We test the listing with that example request before it can be badged settlement-verified. Automated checks run first, then a person reviews it, and you get one email with the result. Listing is free. Tunnels and sandbox hosts are not accepted.

Does PayAPI Market take a cut?

No. Listing is free and there is no per-request fee. Each call is paid by the agent straight to the wallet in your 402 challenge, settled in USDC on Base, Solana, Algorand or Polygon if your route accepts them, so PayAPI takes 0% of each job. PayAPI Market is not in the payment path and never holds your funds.

What does settlement-verified mean for my listing?

After review, PayAPI Market pays one cheap call on one route, up to $0.10, from its own wallet. If real product comes back and the money lands in your listed wallet, the listing goes live with a settlement-verified badge. The badge is that on-chain receipt on Base, not a health ping. It covers the route we paid. Other routes on your listing stay unverified until paid. Tests priced above $0.10 are not paid from PayAPI's canary wallet, and a payment from another wallet is not accepted. Send the test price plus 20% in USDC on Base to 0x171d8021b98c53DCbB3c9C30CBbBeb1b01850fCA. We will email you once the top-up arrives, then run one paid test of this route. A listing depends on that test passing review.

Do I need to write Solidity or any blockchain code?

No. You need a route that answers unpaid requests with a valid x402 HTTP 402 challenge that pays your Base USDC wallet. Standard x402 middleware for TypeScript, Python or Go handles the challenge, payment check and settlement, so you set a price per route and keep your existing API code.

Can I keep my existing API and just add x402 in front of it?

Yes. You can add x402 middleware to your current server, or run a thin gateway in front of it that returns the 402 and forwards paid requests. Your application code can stay as it is. What matters for listing is a durable URL whose paid route returns a valid 402 to your wallet.

How do I get paid out from USDC to my bank?

Payments arrive as USDC in the wallet you listed for that network, call by call, with no monthly batching. To turn USDC into pounds or dollars, send it to an exchange that supports USDC on Base, such as Coinbase, and withdraw to your bank. PayAPI Market never holds your funds at any point.

What happens if my API goes down?

You stop earning while it is down, and PayAPI Market never charges you for downtime. Every search and listing result carries a reliability score built from paid verifications, health history and payment-address integrity, so sustained failures lower how agents see your listing. Fix the route and the score can recover.

Providers with a live listing