---
title: "Tokens whose symbol and decimals the API knows"
method: GET
path: "/v1/supported-tokens-registry"
tags: ["Reference"]
---

# Tokens whose symbol and decimals the API knows

`GET /v1/supported-tokens-registry`

## Request

- Base URL: `https://intelapi.publicaml.org`
- URL: `https://intelapi.publicaml.org/v1/supported-tokens-registry`
- Auth: one of:
  - API key in header `X-API-Key`
  - none

The contracts enrichment can name and denominate. Anything outside this list falls back to 18 decimals and a null symbol, which is why an amount for an unlisted token may be wrong — check here before showing one.

## Query parameters

- `chain` 'bitcoin' | 'ethereum' | 'bsc' | 'tron': Which blockchain the address belongs to. Send one of the four values in the enum. The short forms used by the older clients (ETH, BTC, TRX, BNB) and any capitalisation are still accepted, but responses always echo the canonical spelling. Getting this wrong is the single commonest integration bug: the same 0x-prefixed address exists on ethereum, bsc and tron and means a different wallet on each, so the chain is part of the identity, never a hint. If it does not match the address format the call fails with `invalid_address_format`, which names the chain the address does look like.

## Response `200`

The registry.

- object

## Other responses

- `400`: Malformed request.
- `429`: Rate limited: anonymous callers, and keys issued with a quota of their own. Authenticate to remove the limit.
- `500`: Server error.

---

[API](https://skmtc.dev/publicaml/apis/publicaml-intelligence-api.md) · [All operations](https://skmtc.dev/publicaml/apis/publicaml-intelligence-api/llms.txt) · [OpenAPI document](https://skmtc.dev/publicaml/apis/publicaml-intelligence-api/revisions/7c0c6315088c?raw)