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.
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.
Request
integer
required
The destination chain to check coverage on.
Response
integer
Echoes the requested chain.
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.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.