> ## 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.

# RAVN Integrator API

> One integration to swap any asset across any chain — EVM, Solana, and native Bitcoin.

RAVN aggregates RFQ market makers, intent networks, and bridges behind a single, uniform
interface. Quote, execute, and track a swap across EVM, Solana, and **native Bitcoin** —
without ever touching a bridge, a wrapped asset, or a synthetic.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Swap 1 ETH → SOL end to end in four calls.
  </Card>

  <Card title="Execution types" icon="code-branch" href="/execution-types">
    The one field your integration branches on.
  </Card>

  <Card title="API Reference" icon="terminal" href="/api-reference/overview">
    Every endpoint, request, and response.
  </Card>

  <Card title="Pricing" icon="tag" href="/pricing">
    Route-based fees, fully transparent.
  </Card>
</CardGroup>

## Base URL

```
https://app.ravn.exchange/api/v1
```

* **Content type:** `application/json`
* **Amounts:** always strings, in the token's **smallest unit** (wei, lamports, satoshis).
* **Native coin:** use the sentinel `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` (for Solana native SOL, use its mint `So1111...1112`).

<Note>
  RAVN is in beta. During beta the API is **open** — no API key required. Fees are shown
  transparently in every quote and are invisible to your end users.
</Note>

## Why it's different

Most swap APIs do one thing — an EVM transaction — so their whole surface assumes it. RAVN
spans three genuinely different settlement worlds, and every quote resolves to exactly one
`executionType`. Your integration reads that one field and branches. That's the whole contract.

| Model         | What the user does                      | Venues                        |
| ------------- | --------------------------------------- | ----------------------------- |
| `TRANSACTION` | Sign & broadcast                        | Across, Relay, Mayan, Jupiter |
| `SIGNATURE`   | Sign typed data (no gas) → RAVN submits | 0x Gasless, Bebop, CoW        |
| `DEPOSIT`     | Send the origin asset to an address     | NEAR Intents, Rift (BTC)      |

## The response envelope

Every response has the same shape.

<CodeGroup>
  ```json Success theme={null}
  { "data": { }, "meta": { "requestId": "uuid", "version": "2024-01" } }
  ```

  ```json Failure theme={null}
  { "error": { "code": "NO_LIQUIDITY", "message": "…" },
    "meta": { "requestId": "uuid", "version": "2024-01" } }
  ```
</CodeGroup>

Every response also carries `x-request-id` and `ravn-version` headers. Log the `requestId` —
quote it when contacting support.