Skip to main content
Paid x402 routes are priced from each upstream provider’s public PAYG schedule plus a flat gateway settlement surcharge of $0.0006 per paid call. This surcharge covers the Solana transaction cost required to settle each exact-payment request. x402 paid routes settle in USDC on Solana mainnet. Ryvo channel routes are denominated in official devnet USDC token amounts and settle later through Ryvo Protocol bundle settlement.

​
Alchemy - Compute Unit pricing

Alchemy routes are priced on their Solana PAYG compute-unit schedule.
  • Reference price: $0.45 per 1,000,000 CU
  • Pricing source checked: official Alchemy Solana PAYG docs on 2026-04-18.
Per-method Compute Units used by the gateway:

​
RPC

​
DAS

The per-call USDC price is:
Where the numerator is in USDC micro-units (six decimal places), and 600 micro-USDC is the flat transaction-fee surcharge.

​
Helius - per-credit pricing

Helius routes are priced on their additional-credits schedule.
  • Reference price: $5 per 1,000,000 credits
  • Pricing source checked: official Helius docs on 2026-04-18.
Per-method credits used by the gateway:

​
RPC

​
DAS

​
Helius Wallet API

Helius Wallet API routes are available on mainnet and devnet path families. Every route costs the same flat amount. Per-call USDC price:
Again, 600 micro-USDC is the fixed surcharge applied to every x402 paid route.

​
Tokens API - no per-call price

Tokens API routes are auth-only. The gateway holds the Tokens API key server-side and exposes it to clients via a SIWX signature. There is no per-request USDC settlement. Tokens API routes still sit behind the x402 challenge/response flow, the client must present a valid wallet signature, but no transfer is created. See Access modes for the mechanics.

​
Ryvo channel pricing

For /v1/ryvo-channel/... routes, the catalog publishes token-denominated pricing: V1 channel prices are derived 1:1 from the existing USD schedule into nominal devnet USDC amounts, then compared as integer six-decimal token amounts. Tokens API routes remain SIWX/auth-only and do not use payment channels.

​
How prices are advertised

Every x402 paid route advertises its price in two places:
  1. In the route’s 402 Payment Required envelope as maxAmountRequired, expressed in micro-USDC.
  2. In the catalog entry as priceUsd, expressed as a decimal string.
Clients that use @x402/fetch or any x402 library will pick up the price automatically from the challenge envelope, there is no need to hard-code prices. Channel-backed routes advertise priceTokenAmount in the catalog and require the client to increment its signed cumulative commitment by exactly that amount.

​
See also