Sato Hub
Pay-per-request APIs

x402 Merchants

Find APIs that accept x402 payments, ranked by what we observed on Base.

  • Merchants indexed4,145
  • Answer HTTP 4021,518
  • Paid by outside payers · 7dn/a

Which x402 APIs get paid by outside payers?

As of 2026-11-20, we hold no Base payments reading for any seller wallet yet, and 1,518 of the 1,944 seller wallets we checked answered HTTP 402 when we asked.

Top of the evidence order

  1. #1
    opendata402.com Base, Arbitrum, Polygon · 0x295a…9fb1

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 12 of 12 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-11-09.

  2. #2
    767-2676.com Base · 0x5f5a…3cb8

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 1 of 2 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-10-17.

  3. #3
    agent-treats-production.up.railway.app Base · 0xbd65…36f0

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 2 of 2 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-11-02.

  4. #4
    agentproof-murex.vercel.app Base · 0x9299…1023

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-10-05.

  5. #5
    aiact-api.com Base · 0xe894…c8dd

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-11-17.

  6. #6
    api.24klabs.ai Base · 0xe73d…1114

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 6 of 7 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-11-15.

  7. #7
    api.agentweather.io Base · 0xa15c…f4ec

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-10-26.

  8. #8
    api.aurenic.org Base · 0x594b…4933

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 3 of 3 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-11-20.

  9. #9
    api.automaton-sovereign.workers.dev Base · 0x71de…e528

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-11-07.

  10. #10
    api.basefeed.io Base · 0xefc3…360e

    Payments: unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)). 402 check: 3 of 3 probed endpoints answered HTTP 402 with a parseable payment payload, checked 2026-11-18.

Payments are measured on Base only; other chains show unknown. x402-style payments are counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too. A payment count describes what we observed, not the quality of the service.

4,145 merchantsRanked by evidenceHow we rank1Paid by 3 or more outside payers on Base, with no single payer above 90%.2Endpoints answer HTTP 402 when we ask.3Everything else. No reading ranks above a “no”.Endpoint count and payments to us never move a merchant.as of

  1. #1
    opendata402.com Base, Arbitrum, Polygon · 0x295a…9fb1

    Payments unknown / Answers 402 (2026-11-09) / 150 endpoints, from $0.001 per request

  2. #2
    767-2676.com Base · 0x5f5a…3cb8

    Payments unknown / Answers 402 (2026-10-17) / 4 endpoints, $0.001 per request

  3. #3
    agent-treats-production.up.railway.app Base · 0xbd65…36f0

    Payments unknown / Answers 402 (2026-11-02) / 7 endpoints, from $0.001 per request

  4. #4
    agentproof-murex.vercel.app Base · 0x9299…1023

    Payments unknown / Answers 402 (2026-10-05) / 1 endpoint, $0.001 per request

  5. #5
    aiact-api.com Base · 0xe894…c8dd

    Payments unknown / Answers 402 (2026-11-17) / 1 endpoint, $0.001 per request

  6. #6
    api.24klabs.ai Base · 0xe73d…1114

    Payments unknown / Answers 402 (2026-11-15) / 13 endpoints, from $0.001 per request

  7. #7
    api.agentweather.io Base · 0xa15c…f4ec

    Payments unknown / Answers 402 (2026-10-26) / 54 endpoints, from $0.001 per request

  8. #8
    api.aurenic.org Base · 0x594b…4933

    Payments unknown / Answers 402 (2026-11-20) / 6 endpoints, from $0.001 per request

  9. #9
    api.automaton-sovereign.workers.dev Base · 0x71de…e528

    Payments unknown / Answers 402 (2026-11-07) / 5 endpoints, from $0.001 per request

  10. #10
    api.basefeed.io Base · 0xefc3…360e

    Payments unknown / Answers 402 (2026-11-18) / 3 endpoints, from $0.001 per request

  11. #11
    api.borisinc.com Solana · XcPUkn…kJwo

    Payments unknown / Answers 402 (2026-11-11) / 1 endpoint, $0.001 per request

  12. #12
    api.clinkforge.com Base · 0xf3d6…32cc

    Payments unknown / Answers 402 (2026-10-04) / 26 endpoints, from $0.001 per request

  13. #13
    api-v2.ixs.finance Base · 0xe341…9f73

    Payments unknown / Answers 402 (2026-10-10) / 1 endpoint, $0.001 per request

  14. #14
    api.getsly.ai Base · 0xed18…57b7

    Payments unknown / Answers 402 (2026-09-27) / 1 endpoint, $0.001 per request

  15. #15
    api.govparse.io Base · 0x3873…7129

    Payments unknown / Answers 402 (2026-11-16) / 5 endpoints, $0.001 per request

How we rankShowHide

One card per seller wallet, with the chains it is registered on. The order uses what we observed and nothing else: first sellers with x402-style payments from several outside payers on Base, then sellers whose endpoints answered HTTP 402 when we asked, then the rest. Ties go to the lower price. Listing count, the seller’s own wording and any payment to us never move a merchant.

Answers 402
Whether the listed endpoints answered HTTP 402 with a parseable payment payload when we asked. Each reading carries its date. We never send a payment, so we never observe delivery.
Outside payers
x402-style payments, 7-day window (Base): payments, payers and USDC from an exact read of the window. Wallets we pay from are removed before counting. Method: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too. Chains other than Base show unknown because we do not measure them yet. USDC that reached the seller wallet by other routes is shown on each profile as context and never moves a merchant.
Unknown
A blank means we hold no reading. It is never counted as a failure and never ranked below a reading that says no.
Owner claimed
The seller wallet signed a message for this page. It proves control of that key and says nothing about the service.
Categories
Assigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
Prices
The price each endpoint registered in the catalogue, decoded for USDC on Base and Solana. A listed price is not an observed charge.
Related
Declared endpoints that answer · x402 payment processors · Trust rules

Data CC-BY-4.0, attribution: data by satohub.ai. Sellers come from the CDP Bazaar and x402 List. Data: x402-list.com (CC BY 4.0). Appearing here is not an endorsement. The same list is at /api/x402/merchants. Sell an x402 API? Run the endpoint doctor to see what a buyer’s client sees.

Questions this page answers

Which x402 endpoints answered a paid request recently?
Sato Hub does not observe a paid request being answered; what it records is this. As of 2026-11-20, we hold no Base payments reading for any seller wallet yet, and 1,518 of the 1,944 seller wallets we checked answered HTTP 402 when we asked. Payments are counted on Base only; delivery after payment is not measured here, and a payment observed is not proof that the endpoint delivered. Sellers are listed one per payout address on /x402/merchants, with each reading dated.
What does 'answered HTTP 402' mean here?
That on the date shown, an unpaid request to one of the seller's endpoints got status 402 and a payment payload a client could parse. Nothing was paid, so it says the endpoint asked for payment, not that paying returns what was sold.
How are payments to a seller counted?
A transaction on Base counts when it carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses, and its payer is not one of ours. A seller is ranked as paid by outside payers only with at least 3 outside payers and no single payer above 90% of the USDC. Other chains are not measured, and a blank reading is unknown, not zero.