9 keyless facilitators · 13 chains · every one live-settled
9 keyless facilitators across 13 chains — no API key, no account, no registration. Every entry was verified by settling a real payment, not by reading a status endpoint.
And the shortest answer: with PipRail you don't need one at all.
A facilitator verifies and settles an x402 payment for you. It is a convenience, not a requirement. PipRail verifies payments locally against your own RPC, so the default path has no facilitator, no backend and no third party holding your money. The x402 v2 spec agrees — §7 says a resource server may host the verify and settle endpoints itself.
You want a facilitator for exactly one reason: the ratified gasless
exact scheme,
where somebody has to sponsor the gas and you would rather that were not your relayer key.
The coverage table below
is who can do that, and where.
Sorted by how many keyless options each chain has. Every entry records the day we settled through it, and 25 carry a transaction you can open on a block explorer.
eip155:8453
facilitator.ultravioletadao.xyz
Live-settled · Base USDC EIP-3009
2nd UVD validation chain (after HyperEVM).
x402.dexter.cash
Live-settled · Base USDC EIP-3009
facilitator.goplausible.xyz
Live-settled · Base USDC EIP-3009
2nd GoPlausible validation chain (after Algorand).
facilitator.cascade.fyi
Live-settled · Base USDC EIP-3009
eip155:137
facilitator.payai.network
Live-settled · Polygon native USDC EIP-3009
facilitator.ultravioletadao.xyz
Live-settled
eip155:42161
facilitator.payai.network
Live-settled · Arbitrum native USDC EIP-3009
facilitator.ultravioletadao.xyz
Live-settled
eip155:43114
facilitator.payai.network
Live-settled · Avalanche native USDC EIP-3009
x402.dexter.cash
Live-settled
No floor hit at $0.001 here.
eip155:56
x402.dexter.cash
Live-settled
BNB EIP-3009 tokens FDUSD/USD1/U (Binance-Peg USDC/USDT are Permit2 → not facilitator-settleable). Accepts U (verify confirmed 2026-06-21).
facilitator.pieverse.io
Live-settled
BNB EIP-3009 tokens FDUSD/USD1/U (same Binance-Peg caveat as Dexter).
eip155:143
facilitator.ultravioletadao.xyz
Live-settled · Monad native USDC EIP-3009
3rd UVD validation chain.
facilitator.pieverse.io
Live-settled · Monad USDC EIP-3009
eip155:10
facilitator.ultravioletadao.xyz
Live-settled
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
facilitator.payai.network
Live-settled · Solana SPL SVM
algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=
facilitator.goplausible.xyz
Live-settled
Algorand USDCa, atomic-group fee pooling; both buyer AND merchant pay 0 ALGO. The only keyless Algorand x402 facilitator.
eip155:1
facilitator.ultravioletadao.xyz
Live-settled
eip155:999
facilitator.ultravioletadao.xyz
Live-settled · HyperEVM native USDC EIP-3009
eip155:1329
facilitator.payai.network
Live-settled · Sei native USDC EIP-3009
eip155:130
facilitator.ultravioletadao.xyz
Live-settled · Unichain native USDC EIP-3009
Generated from the SDK's own registry, so it cannot drift from what the code does. A chain missing here has no known keyless facilitator — it does not mean x402 will not work there. PipRail's default local verification works on every chain it supports.
The same 28 chain-and-facilitator pairings, indexed by vendor — because half the time you already know the facilitator and want to know where it reaches.
Settles on 8 chains
Settles on 6 chains
Settles on 6 chains
Settles on 2 chains
Settles on 2 chains
Settles on 1 chain
Settles on 1 chain
the official Polygon facilitator
Settles on 1 chain
Settles on 1 chain
The registry ships inside @piprail/sdk — the page above is
generated from it, so what you read here is what your program gets.
Look one up
import { knownFacilitatorsFor, firstKeylessFacilitator } from '@piprail/sdk'
// Every keyless facilitator we have live-settled through, on one chain.
knownFacilitatorsFor('eip155:8453')
// → [{ url: 'https://facilitator.payai.network', keyless: true,
// schemes: ['exact'], settles: ['eip3009'], note: '…' }, …]
// Or just the first one that speaks a given settlement method.
firstKeylessFacilitator('solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp', 'svm')?.url
// → 'https://facilitator.payai.network'
firstKeylessFacilitator('eip155:999999') // unknown network
// → undefinedOr skip facilitators entirely
import express from 'express'
import { requirePayment } from '@piprail/sdk'
const app = express()
// The DEFAULT rail. No facilitator, no backend, no third party:
// the buyer broadcasts, and you verify against your OWN RPC.
app.get('/report',
requirePayment({ chain: 'base', token: 'USDC', amount: '0.05', payTo }),
(req, res) => res.json({ unlocked: true }),
)
// Want the gasless rail too? Offer both and let the agent pick.
// Only THIS one needs a facilitator (or your own relayer key).
app.get('/premium',
requirePayment({
chain: 'base', token: 'USDC', amount: '0.05', payTo,
schemes: ['onchain-proof', 'exact'],
}),
(req, res) => res.json({ unlocked: true }),
)Full reference in the facilitator coverage docs, and the gasless rail is explained end-to-end in gasless payments.
The things people actually ask before choosing one.
A facilitator is a third-party service that verifies and settles an x402 payment on your behalf. It exposes two endpoints — POST /verify and POST /settle — and, on a gasless "exact" rail, it also sponsors the gas so neither the buyer nor the seller pays it. It is a convenience, not a requirement: x402 v2 §7 explicitly allows a resource server to host those endpoints itself.
No. PipRail verifies payments locally against your own RPC, so you can accept x402 with no facilitator, no backend and no third party in the path. A facilitator is only needed when you want the ratified gasless "exact" scheme and would rather not run a relayer key yourself.
Call requirePayment() with your chain, token, amount and your own wallet address, and point the SDK at your own RPC URL. The 402 challenge, the proof check and the replay guard all run inside your process: PipRail reads the transaction from the RPC you chose, re-derives every field from the challenge it issued, and checks a single-use proof set. No third party verifies, settles, or sees the payment, and the money moves from the payer's wallet to yours in one on-chain transfer. x402 v2 §7 permits this explicitly — "resource servers MAY host the endpoints themselves" — so a facilitator-free deployment is spec-conformant, not a workaround. The trade-off is gas: with nobody sponsoring it the buyer pays their own, so if you want the buyer to pay nothing you either use a facilitator or run the fee-payer key yourself on a self-settled "exact" rail.
No. Coinbase runs the best-known x402 facilitator, which is why most guides assume it, but the protocol requires no account with anyone. PipRail ships no vendor coupling at all: there is no signup, no API key, no dashboard and no CDP dependency. You install an npm package, name a chain, and payments settle to a wallet whose keys you hold. If you do want a facilitator, PipRail routes to keyless ones that also need no account.
Keyless means the facilitator requires no API key, no account and no registration — you point at the URL and it settles. Every facilitator listed here is keyless. A facilitator that demands an API key couples your payment rail to a vendor relationship, which is the thing x402 exists to avoid.
13 chains have at least one known keyless facilitator: Base, Polygon, Arbitrum, Avalanche, BNB Chain, Monad, Optimism, Solana, Algorand, Ethereum, HyperEVM, Sei, Unichain. Base has the most options with 6.
EIP-3009 (transferWithAuthorization) lets a token holder sign a transfer off-chain and let somebody else submit it and pay the gas. It is what makes the x402 "exact" scheme gasless for the buyer: you sign, the facilitator submits. Native USDC implements it on most chains, which is why almost every facilitator below settles eip3009 rails. A chain whose USDC is a bridged wrapper usually cannot do this, which is why coverage is uneven.
The Bazaar is a discovery index of payable x402 endpoints — it answers "what can I buy?". A facilitator answers "who will settle my payment?". They are different layers and you can use either, both, or neither. PipRail emits a bazaar-compatible extensions.bazaar block on every 402 it serves, so a PipRail endpoint is discoverable without any facilitator being involved.
Every entry was verified by settling a real payment through the facilitator on the date recorded against it — not by reading its /supported endpoint and assuming. 25 settlements carry a transaction hash you can open on a block explorer, and all 25 were re-confirmed on-chain on 2026-08-28. Entries are only added after a live settlement succeeds.
It gets removed. A registry that only ever grows is how a dead endpoint survives in it: on 2026-08-28 a liveness sweep found two seeded facilitators had died — one had gone NXDOMAIN, the other pointed at a deleted container — and one of them was first in the Monad list, so the SDK was handing callers a dead URL. Both were removed in @piprail/sdk, regression tests now assert they can never come back, and the sweep is re-run before releases that touch facilitator routing.
Where this fits in the rest of PipRail.
The full chain and token matrix — including the many chains that need no facilitator at all.
Accept x402 in a few lines, verified against your own RPC. No backend, no fee.
Give an AI agent a budget-bound wallet that can pay x402 URLs on its own.
How a PipRail 402 describes itself so agents and indexes can find it.
A real payable URL you can hit right now — dual-rail, on mainnet.
Per-chain settlement methods, the self-settle alternative, and the API reference.
The default rail needs no facilitator, no backend, and no account — just your own RPC.
Accept x402 without a facilitator
Like & share PipRail
Star on GitHub Follow @piprailhq