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.
Not during beta, because the API is open. Just call https://app.ravn.exchange/api/v1. Keys with per-partner fees and rate limits are issued as the program matures. See Authentication.
A small integrator fee scales with the route. It is 0 bps on commodity same-chain swaps and a premium on cross-chain, cross-ecosystem, and native-BTC routes. It is shown transparently in every quote and is invisible to your end users. See Pricing.
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.
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.