Conventions shared by every Routescan endpoint, read this once to call the API correctly.

Base URL and networks#

• {network}, mainnet or testnet.
• {chainId}, the numeric chain id (for example 1 for Ethereum, 43114 for Avalanche C-Chain). See the supported-chains list for every indexed chain.

Multichain queries#

Use {chainId} = all to query across every chain Routescan indexes in a single call. Narrow an all query with includedChainIds / excludedChainIds (comma-separated ids) or ecosystem (e.g. avalanche).

Authentication#

The apikey is sent as an HTTP header, not a query parameter. It is optional on the free tier; an API key raises your rate limits.

Rate limits#

• The free tier needs no API key; an API key raises your limits.
• Paid plans raise these further. A 429 means you have been rate limited. See Rate limits.

Pagination#

List endpoints are cursor-paginated and return a link object:

• Pass link.nextToken back as the next query parameter for the following page (and prevToken as prev).
• limit controls page size; count=true includes a total count where supported.

Errors#

Non-2xx responses carry an error message in the body. Always check the HTTP status code before parsing the response.

Machine-readable resources#

• OpenAPI spec: https://api.routescan.io/v2/documentation/json
• /docs/llms.txt, index of every docs page for LLMs.
• /docs/llms-full.txt, the full documentation as plain text.
• Append .md to any API reference page (e.g. /docs/api/addresses.md) for its Markdown.
• MCP server, see Build with AI.