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

# Supported chains and tokens

> Discover the chains and tokens available through the Routes API.

Use the discovery endpoints before requesting a route. Token listings, chain support, and available liquidity can change independently.

| Endpoint | Use it to |
| - | - |
| [`GET /v1/chains`](/api-reference/v1/chains) | Find supported chain IDs, contract addresses, and quote signers |
| [`GET /v1/tokens`](/api-reference/v1/tokens) | Find listed tokens and their chain-specific addresses |
| [`POST /v1/quotes`](/api-reference/v1/quotes) | Check whether the requested pair and amount can currently be quoted |

These endpoints require an API key. Their reference pages contain request/response examples, authentication requirements, and error handling.

A listed token does not guarantee that every pair or amount has an executable quote. Identify assets by both chain ID and address; a shared symbol alone is not sufficient.

## Chain identifiers

Use the chain IDs returned by the API. The Routes API uses `1399811149` for Solana. A bridge's messaging domain, such as a Circle domain or LayerZero endpoint ID, can differ from the API chain ID.

## Product coverage

Routes, Programmable Addresses, and Sauce have separate deployment and availability requirements. Use the relevant product guide when planning an integration:

* [Programmable Addresses](/programmable-addresses/overview)
* [Sauce deployments](/programmable-transactions/sauce/architecture-and-deployments#deployments)
* [Verified Liquidity](/verified-liquidity/overview)

## Next steps

[Request a quote](/api-reference/v1/quotes) or [make your first transfer](/get-started/first-transfer).


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