# Chains and Assets

Use the chain registry before creating a payment.

## List Chains

```bash
curl "https://mock.artum.app/v1/chains" \
  -H "Authorization: Bearer $ARTUM_MOCK_API_KEY"
```

## List Assets

```bash
curl "https://mock.artum.app/v1/chains/bsc-mainnet/assets" \
  -H "Authorization: Bearer $ARTUM_MOCK_API_KEY"
```

Example response:

```json
{
  "data": [
    {
      "asset": "bsc-usdt",
      "chain": "bsc-mainnet",
      "symbol": "USDT",
      "decimals": 18,
      "token": {
        "address": "0x55d398326f99059ff775485246999027b3197955",
        "decimals": 18
      },
      "enabled": true
    }
  ]
}
```

## Chain Keys

Public API requests use chain keys such as:

```
bsc-mainnet
```

Do not use EVM numeric chain IDs in API requests unless a specific endpoint asks for them.

## Asset Keys

Asset keys are chain-local public identifiers such as:

```
bsc-usdt
```

Use the asset registry response as the source of truth for token address, decimals, and display metadata.

Do not hardcode token decimals in your integration. See [Amounts and Decimals](/concepts/amounts-and-decimals.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.artum.app/concepts/chains-and-assets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.