Skip to main content
No. RAVN routes only through RFQ market makers, intent networks, and solver and relayer networks that settle in the canonical asset. There is never a lock-and-mint bridge, wrapped token, or synthetic.
No. The user signs or sends directly to the venue, and RAVN never holds funds. See the Security Model.
No, but get one anyway. Every call works with no x-api-key header, rate-limited by IP, but a free key takes 30 seconds, no review, and instantly quadruples your limit, plus it puts your project on RAVN’s radar for a future partnership or rev-share deal. See Authentication.
RAVN charges 0 bps on every route, for every integrator, by default. The fee object still appears on every quote; it just always reports 0. See Pricing for the route table and how optional x402 call fees differ from the swap fee.
An opaque, signed handle returned by /quote. Pass it back to /execute verbatim, and never parse it. It is tamper-evident and it expires.
Branch on the executionType field from /execute. The values are TRANSACTION (sign and broadcast), SIGNATURE (sign typed data, then RAVN submits it), and DEPOSIT (send the origin asset to an address). That single field is the whole client contract. See Execution Types.
Yes. On RFQ and gasless venues, the user signs an off-chain message and a solver covers gas. They only need the asset they are selling.
EVM chains, Solana, and native Bitcoin. See Supported Chains & Venues. The /health endpoint reports the live venue set.
Poll GET /status with the statusRef from /execute or /submit-signature. It returns a normalized lifecycle of pending, processing, then success. Stop only on a terminal state: success, refunded, or failed. A lapsed deal reports expired first (a refund is owed but not yet issued), so keep polling until it becomes refunded.
Every response includes a requestId, which is also in the x-request-id header. Include it when you reach out via ravn.exchange, and we can trace the exact request.