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

# GET /tokens/btc-coverage

> Which tokens on a chain actually route from native Bitcoin.

For a swap where native BTC is the **source**, not every token on the destination chain is
reachable. This returns which of RAVN's listed tokens on `chainId` a BTC venue can actually
route to, and how many venues serve each, so you can build a token list that matches what will
really quote instead of discovering it one failed `NO_LIQUIDITY` at a time.

<Note>
  BTC-as-source only. Selling a token **into** BTC isn't restricted the same way (nearly any
  token can be sold into BTC), so this endpoint has nothing useful to say about that direction.
</Note>

## Request

<ParamField query="chainId" type="integer" required>The destination chain to check coverage on.</ParamField>

No API key required (see [Authentication](/authentication) for the optional higher-limit tiers).

```bash theme={null}
curl -s "https://app.ravn.exchange/api/v1/tokens/btc-coverage?chainId=8453"
```

## Response

<ResponseField name="chainId" type="integer">Echoes the requested chain.</ResponseField>
<ResponseField name="filtered" type="boolean">False means the upstream venue lists couldn't be reached right now, so `coverage` is empty and the answer is unknown, not "nothing routes." Treat this the same way you'd treat an outage: show your full token list rather than let it look like zero coverage.</ResponseField>
<ResponseField name="coverage" type="object">Lowercased token address to the number of BTC venues (1 to 3) that route to it. Tokens no venue serves are omitted entirely, not listed at 0.</ResponseField>

```json theme={null}
{
  "data": {
    "chainId": 8453,
    "filtered": true,
    "coverage": {
      "0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee": 2,
      "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913": 2,
      "0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf": 2
    }
  }
}
```

<Tip>
  Higher counts are the safer bet: a token two or three venues cover is more likely to keep
  routing if one venue has an outage. Rank your token list by count, the same way RAVN's own
  picker does.
</Tip>