- No key to provision, rotate, or leak. Nothing to store server-side; a compromised agent process has no standing secret to revoke.
- Spend is capped per call, not per key. Each payment authorizes exactly one request for exactly the price quoted; there’s no API key that, once leaked, keeps working until someone notices and rotates it.
- The payment itself is the audit trail. Every call settles on-chain (Base or Solana), so usage is independently verifiable without RAVN-side logging or an API dashboard.
- Discoverable by other agents, not just yours. RAVN’s x402 routes are indexed in Coinbase’s x402 Bazaar catalog (the search and merchant-lookup API behind agentic.market) and listed on x402scan.com, so agents that discover services by querying that catalog directly can find and call RAVN without being told about it in advance. Whether RAVN also appears in agentic.market’s own curated marketplace UI is a separate, usage-driven decision on their end, not something indexing alone guarantees. The free REST/MCP doors aren’t part of the Bazaar catalog at all.
Endpoints
Only quote and execute are metered over x402.
status and health aren’t priced endpoints and
have no /x402/ counterpart — call GET /v1/status and
GET /v1/health directly (free, no key) once you’ve paid to execute.
Request and response bodies are identical to the free endpoints: same fields, same DTOs, same
error codes. The quoteToken from /v1/x402/quote works interchangeably with either
/v1/execute or /v1/x402/execute: you can get a free quote and only pay to execute, if you
want.
The price is a flat access fee for the API call itself; it is not RAVN’s swap fee, which
stays 0% on every route regardless of which door you come through.
Accepted payment
How it works
x402 repurposes the HTTP402 Payment Required status code:
- Call the endpoint with no payment attached.
- RAVN responds
402with apayment-requiredheader describing accepted payment options (network, asset, amount, recipient). - Your x402 client signs a payment (an EIP-3009 USDC authorization on Base, or a Solana USDC
transfer) and retries the request with a
payment-signature-style header attached. - RAVN verifies and settles the payment via its facilitator, then executes your original request and returns the normal response.
fetch.
Example
@x402/svm) to pay from a Solana wallet instead.

