Copy prompt
Open in Claude
Open in ChatGPT
Open in Perplexity
Pricing
$5 per million requests, all methods, all chains. Each call debits 5 atomic USDC ($0.000005) from your Circle Gateway balance. Settlement is gasless on your side, and Circle batches settlements on Goldsky’s side.Endpoint
Edge RPC endpoints follow a single URL pattern, with the chain ID in the path:edge.goldsky.com with no path. It returns a JSON list of every supported network, with CAIP id, alias, block time, and health status:
Supported chains for x402 payments
You can pay over x402 on any chain Circle Gateway currently advertises. The 11 networks below mirror the live list athttps://gateway-api.circle.com/v1/x402/supported; Edge serves additional chains that aren’t yet in this list, and those still require a regular API key.
You only need a Circle Gateway USDC deposit on one of these chains. The endpoint advertises every chain in its 402 response, and SDK clients pick whichever you’re funded on.
Quickstart
1. Fund a Circle Gateway deposit
Use the Circle Gateway dashboard, or do it directly via the SDK:/v1/balances API after the on-chain transaction confirms.
2. Pay for an Edge request
pay() handles the full 402 → sign → retry flow for you:
How it works
x402 is an HTTP protocol layered on top of standard requests. The full handshake:1
Initial request returns 402
Your client sends an unauthenticated request. Edge responds with HTTP 402 and a body listing every accepted (chain, asset) option:
2
Sign an EIP-712 authorization
Your client picks an
accepts entry it can satisfy (typically the chain your Gateway deposit lives on) and signs an EIP-712 TransferWithAuthorization message against the GatewayWalletBatched contract from the extra block.3
Retry with Payment-Signature header
Your client base64-encodes the signed payload and resends the original request with one extra header:Edge forwards the payment to Circle’s facilitator for settlement, then proxies the RPC request to upstream providers and returns the response with HTTP 200.
Limits and operational notes
- Authorization validity window: Circle Gateway requires the signed authorization’s
validBeforeto be at least ~4 days in the future. Edge advertisesmaxTimeoutSeconds: 604800(7 days) so SDK defaults work out of the box.