Skip to main content
This page documents every route exposed by the deployed gateway. Paid Solana routes are enumerated programmatically at GET /v1/catalog — the full matrix is documented in Routes.

​
Public endpoints

​
Health

​
GET /healthz
route
Returns { ok: true, service: "agon-gateway", status: "healthy" }. Use this as a liveness probe.

​
Catalog

​
GET /v1/catalog
route
Returns every enabled route with its access mode, price, and schemas. Supports ?provider=alchemy|helius|tokens. See Catalog.

​
Solana RPC

​
POST /v1/x402/solana/{cluster}/{provider}/rpc/{method}
route
Paid Solana RPC proxy. cluster ∈ mainnet, devnet. provider ∈ alchemy, helius. method ∈ getBalance, getAccountInfo, getTransaction, getSignaturesForAddress, getTokenAccountsByOwner, getProgramAccounts. Access mode exact. See Solana RPC routes.

​
Solana DAS

​
POST /v1/x402/solana/{cluster}/{provider}/das/{method}
route
Paid Solana DAS proxy. cluster ∈ mainnet, devnet (Alchemy DAS is mainnet-only). provider ∈ alchemy, helius. method ∈ getAsset, getAssetsByOwner, searchAssets. Access mode exact. See Solana DAS routes.

​
Tokens API

​
GET /v1/x402/tokens/...
route
Wallet-authenticated Tokens API proxy. Access mode siwx. See Tokens API routes for the full list.
​
POST /v1/x402/tokens/assets/market-snapshots
route
Batch lookup cached market snapshots for Solana mints. Access mode siwx. mints + addresses combined must contain 1–250 ids.

​
Internal endpoints (server-to-server only)

These routes are not part of the public surface. They are gated by the x-agon-internal-secret header and do not appear in GET /v1/catalog.
​
GET /api/internal/facilitator/supported
internal
Returns supported settlement networks and schemes of the internal facilitator signer.
​
POST /api/internal/facilitator/verify
internal
Verifies an x402 payment payload without submitting it on-chain.
​
POST /api/internal/facilitator/settle
internal
Submits a previously verified x402 payment on-chain using the internal facilitator wallet.
See Facilitator for when to enable these and how to secure them.

​
CORS and OPTIONS

Every public route supports OPTIONS preflight with Access-Control-Allow-Origin: * and the following headers:
  • Allow-methods: the route’s canonical method plus OPTIONS.
  • Allow-headers: Content-Type, PAYMENT-SIGNATURE, X-PAYMENT, X-PAYMENT-RESPONSE, PAYMENT-RESPONSE, SIGN-IN-WITH-X, Authorization.
  • Expose-headers: Content-Type, WWW-Authenticate, X-PAYMENT-RESPONSE, PAYMENT-RESPONSE.
HEAD is accepted on every route that accepts GET, and returns the same headers with an empty body.

​
Discovery

CDP’s Bazaar crawler is supported. Paid routes return 402 Payment Required even for empty-body probes, so the crawler can inspect schemas and prices without triggering settlement.

​
See also