> For the complete documentation index, see [llms.txt](https://docs.liqd.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liqd.ag/liquidswap-integration/token-list.md).

# Token List

Returns tracked tokens and metadata for a chain.

**Endpoint:** `GET https://api.liqd.ag/tokens`

**Authentication**: None required — publicly accessible

**Rate Limits**: No rate limits

### Required Parameters

| Name      | Type   | Description                                                 | Required | Example |
| --------- | ------ | ----------------------------------------------------------- | -------- | ------- |
| `chainId` | number | Chain to query (`999` = HyperEVM, `4663` = Robinhood Chain) | Yes      | `999`   |

### Optional Parameters

| Name       | Type    | Description                               | Default |
| ---------- | ------- | ----------------------------------------- | ------- |
| `search`   | string  | Filter tokens by address, name, or symbol | none    |
| `limit`    | number  | Maximum number of tokens to return        | none    |
| `offset`   | number  | Pagination offset                         | `0`     |
| `metadata` | boolean | When `"false"`, returns only addresses    | true    |

> **Note:** Tokens are sorted by 24-hour transfer count in descending order.

**Example Requests:**

```
GET https://api.liqd.ag/tokens?chainId=999
GET https://api.liqd.ag/tokens?chainId=4663
GET https://api.liqd.ag/tokens?chainId=999&limit=10
GET https://api.liqd.ag/tokens?chainId=999&offset=10&limit=10
GET https://api.liqd.ag/tokens?chainId=999&search=HYPE
GET https://api.liqd.ag/tokens?chainId=4663&search=WETH
GET https://api.liqd.ag/tokens?chainId=999&metadata=false
```

### Response Fields

| Field                                           | Description                                 |
| ----------------------------------------------- | ------------------------------------------- |
| `success`                                       | Whether the request succeeded               |
| `data.chainId`                                  | Chain that was queried                      |
| `data.tokens`                                   | Token list when `metadata` is not `false`   |
| `data.tokens[].address`                         | Token contract address                      |
| `data.tokens[].name` / `symbol` / `decimals`    | Token metadata                              |
| `data.tokens[].isERC20Verified`                 | Whether the token passed ERC20 verification |
| `data.tokens[].transfers24h` / `totalTransfers` | Transfer activity                           |
| `data.addresses`                                | Address-only list when `metadata=false`     |
| `data.count`                                    | Total matching tokens                       |
| `data.limitedCount`                             | Number returned in this page                |
| `data.offset` / `nextOffset` / `hasMore`        | Pagination                                  |
| `data.searchApplied` / `limitApplied`           | Whether filters were applied                |
| `data.serviceStatus`                            | Indexer status                              |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.liqd.ag/liquidswap-integration/token-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.