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

​
Public endpoints

​
Health

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

​
Catalog

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

​
Solana RPC

​
route
Paid Solana RPC proxy. cluster ∈ mainnet, devnet. provider ∈ alchemy, helius. method ∈ getBalance, getAccountInfo, getTransaction, getSignaturesForAddress, getTokenAccountsByOwner, getProgramAccounts (all providers) plus getTransactionsForAddress (Helius-only enhanced history). Access mode exact. See Solana RPC routes.

​
Solana DAS

​
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.

​
Helius Wallet API

​
route
Paid Helius Wallet API identity lookup (mainnet-only). Accepts a base58 address, SNS .sol domain, or ANS custom TLD. Access mode exact, 100 credits per call. See Helius Wallet API routes.
​
route
Paid Helius Wallet API batch identity lookup. Body: { "wallets": string[] } with 1–100 entries. Access mode exact, 100 credits per call.
​
route
Paid Helius Wallet API data routes (mainnet-only). Query params vary per method. Access mode exact, 100 credits per call. See Helius Wallet API routes.

​
Tokens API

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

​
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

x402 discovery crawlers are supported. Paid routes return 402 Payment Required even for empty-body probes, so crawlers can inspect schemas and prices without triggering settlement.

​
See also