> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravn.exchange/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Common questions about the RAVN Integrator API.

<AccordionGroup>
  <Accordion title="Does RAVN use bridges?">
    You always receive the real token, never a wrapped copy (only one you picked, like WBTC,
    which Layerswap's native BTC ↔ WBTC route serves). RAVN runs no bridge of its own. NEAR
    Intents moves coins in and out through its own bridge, so on its routes your deposit is held
    as a matching token on NEAR for the minutes the swap takes. Every quote names the winning
    venue, and you can leave NEAR Intents out with `excludeVenues` if you'd rather. Houdini Swap,
    which only races on private swaps you ask for, routes through two of its partner exchanges,
    which hold the funds for the minutes to an hour the swap takes.
  </Accordion>

  <Accordion title="Is RAVN custodial?">
    No. The user signs or sends directly to the venue, and RAVN never holds funds. See the
    [Security Model](/security).
  </Accordion>

  <Accordion title="Do I need an API key to start?">
    No, but get one anyway. Every call works with no `x-api-key` header, rate-limited by IP,
    but [a free key](/tools/get-api-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](/authentication).
  </Accordion>

  <Accordion title="How do fees work?">
    RAVN itself charges 0 bps, always. Integrators can set their own swap fee on their key (0%
    by default, up to a 100 bps cap) via [`PATCH /v1/keys`](/api-reference/keys) and RAVN pays
    out their share automatically. The `fee` object on every quote reports what was actually
    applied and in which token (`fee.token`, the output token everywhere except Fly Trade and
    Mayan). Payouts go out monthly, in-kind, and only for swaps you reported to `/status` until
    they settled. See [Pricing](/pricing) for the split, payouts, and how optional x402 call
    fees differ from the swap fee.
  </Accordion>

  <Accordion title="What is a quoteToken?">
    An opaque, signed handle returned by `/quote`. Pass it back to `/execute` verbatim, and
    never parse it. It is tamper-evident and it expires.
  </Accordion>

  <Accordion title="How do I handle the different execution types?">
    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](/execution-types).
  </Accordion>

  <Accordion title="Can users swap without holding gas?">
    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.
  </Accordion>

  <Accordion title="Which chains and assets are supported?">
    EVM chains, Solana, and native Bitcoin. See
    [Supported Chains & Venues](/supported). The `/health` endpoint reports the live venue set.
  </Accordion>

  <Accordion title="How do I track a swap to completion?">
    Poll [`/status`](/api-reference/status) with the `quoteToken` that `/execute` returned and
    the `statusRef` from `/execute` or `/submit-signature`, or, for a `TRANSACTION` without one,
    the hash you broadcast. 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`. Do this for every
    swap: the terminal poll is what settles the swap in RAVN's ledger, and only settled swaps
    earn a fee payout.
  </Accordion>

  <Accordion title="Something failed. How do I get help?">
    Every response includes a `requestId`, which is also in the `x-request-id` header. Include it
    when you reach out via [ravn.exchange](https://ravn.exchange), and we can trace the exact
    request.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.