Get supported chains
GET/v1/data/chains
Returns every supported chain with its id, display name and logo. Chain ids are decimal strings, not numbers. Also published as the ChainId schema so it can be code-generated.
Plain-text reference — GET /v1/data/chains
Response 200
| Field | Type | Description |
|---|---|---|
success | True | |
data | object | |
data.count | integer | Number of supported chains |
data.items | object[] | Supported chains, sorted ascending by numeric chainId. |
data.items[].chainId | string | Decimal EVM chain id, as a string. |
data.items[].name | string | Human-readable display name. Prefers the registry shortName (concise, e.g. "eth"); falls back to the long name, then to "Chain {id}". |
data.items[].logoURI | string | Absolute URL to the chain icon. Always populated; consumers should handle broken images gracefully. |
actions | null |
Example response
{
"success": true,
"data": {
"count": 1,
"items": [
{
"chainId": "1",
"name": "eth",
"logoURI": "https://raw.githubusercontent.com/1delta-DAO/chains/main/1.webp"
}
]
}
}
Responses
- 200
- 429
- 500
- 502
Supported chains
Rate limited. Unauthenticated callers share a per-IP budget; send an x-api-key header to lift it. Retry with exponential backoff.
Unexpected server error. Safe to retry with backoff.
An upstream data source or protocol origin failed (error.code is ORIGIN_FAILED). error.details carries the per-origin status. This is also what a missing or malformed required parameter currently returns, rather than a 400.