Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ryvo.network/llms.txt

Use this file to discover all available pages before exploring further.

Ryvo Gateway is a hosted gateway that turns major Solana infrastructure providers and the Tokens API into permissionless HTTP endpoints. Clients do not need upstream API keys; they authenticate and pay through x402, SIWX, or Ryvo Protocol payment channels. What you get:
  • Pay per call with a wallet. x402 Solana RPC and DAS endpoints that you call with USDC on Solana mainnet. No subscriptions, no API keys, no vendor lock-in.
  • Use payment channels for agents. /v1/ryvo-channel/... routes accept signed cumulative commitments against locked official devnet USDC collateral.
  • Sign in with your wallet for free metadata. The Tokens API is exposed over wallet sign-in (SIWX). You prove ownership of a wallet; the gateway calls the Tokens API for you.
  • Transparent pricing. x402 paid routes advertise priceUsd; channel routes advertise priceTokenAmount in official devnet USDC.
  • Pay only on success. If the upstream provider fails, the gateway does not settle the payment. You are never charged for an upstream error.
  • Two providers, one surface. Alchemy and Helius sit behind a common route shape, so you can switch providers or compare latency without changing client code.
  • Non-custodial. The gateway never holds your funds. x402 payments settle directly on Solana; channel collateral stays inside Ryvo Protocol.
  • Standard x402 where appropriate. Anything that speaks x402 works against the x402 routes. Channel routes use Ryvo-specific tooling.

Quickstart

Make your first paid call against the live gateway in minutes.

How it works

Understand the x402 exact and SIWX flows end-to-end.

Routes

Browse Solana RPC, DAS, and Tokens API routes.

Integration guide

Integrate the gateway into your own client or service.

​
When to use the gateway

The gateway is a good fit when any of the following are true:
  • You want paid Solana RPC/DAS access without managing an upstream API key.
  • You want wallet-authenticated access to the Tokens API without shipping an API key.
  • You are building an agent or automated client and want to pay per request from a Solana wallet.
  • You want to prototype an x402 integration against real infrastructure before running your own resource server.
If you want to understand the underlying settlement protocol, Ryvo Protocol, see the Protocol Docs. The gateway is one application-layer example of where Ryvo-style machine payments are useful; the protocol itself is a separate product.

​
Live deployment

FieldValue
Base URLhttps://gateway.Ryvo.network
x402 payment networksolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp (Solana mainnet)
x402 payment assetUSDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v)
Ryvo channel tokenOfficial devnet USDC (4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU)
CatalogGET /v1/catalog
HealthGET /healthz

​
What it is not

  • Not a custodian. The gateway never holds client funds. x402 payments settle directly on Solana; channel collateral remains in Ryvo Protocol accounts.
  • Not the protocol itself. The gateway is an application-layer resource server that can use x402 or Ryvo Protocol channels.
  • Not a token. There is no gateway token. Payments use USDC, either on Solana mainnet for x402 or official devnet USDC for channel testing.

​
See also