Open Sourcestateless routerhosted or self-hosted
One x402 endpoint. Many facilitators.
Keep your existing x402 middleware and payment requirements. The router receives normal facilitator requests, checks the payment network and available auth, then forwards them to PrimeV, x402.org, or CDP.
router statuschecking
import { createCdpAuthHeaders } from "@tunnckocore/x402-router/cdp";
const facilitator = new HTTPFacilitatorClient({
url: "https://x402.wgw.lol",
createAuthHeaders: () =>
createCdpAuthHeaders({
apiKeyId: process.env.CDP_API_KEY_ID,
apiKeySecret: process.env.CDP_API_KEY_SECRET,
}),
});Ethereum Mainnet
PrimeV
1.2s settlement
Base + other EVMs
CDP
pass-through JWT
Solana
CDP
same x402 flow
Test/dev networks
x402.org
live discovery
x402 request->router->PrimeV/x402.org/CDP
x402 v2 only, no seller keys storedWhy it exists
Keep one x402 integration while facilitators keep changing.
Same server flow
Your middleware still talks to a facilitator. The router only decides where each verify or settle request should go.
Seller-owned auth
CDP credentials stay on your server and become short-lived headers. The hosted router does not store seller keys.
Live support list
Supported networks are discovered from upstream facilitators and filtered to x402 v2 before clients see them.
Self-hosting
Hosted by default. Yours when you need it.
The hosted router is ready to use. Self-host the same Worker when you want private infrastructure, custom policy, or non-commercial deployments under the fair-source license.