> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/reference.md).

# Reference

This section explains the key concepts and terminology used throughout the Nansen API.

### Guides

* Supported Chains - Blockchains supported by the API
* Native Tokens - Placeholder addresses, query examples, and coverage limitations
* Address Formats - Address formats for each chain type
* Smart Money Labels - Understanding smart money classifications
* Filter Types - Available filter types and usage
* Sorting - How to sort API results

### Quick Reference

#### Chains

The API supports 37 blockchains:

| Type    | Examples                                         |
| ------- | ------------------------------------------------ |
| EVM     | Ethereum, Arbitrum, Base, BNB, Polygon, Optimism |
| Non-EVM | Solana, Bitcoin, TON, Tron, Starknet, SUI        |

#### Smart Money Labels

| Label                     | Description                                                            |
| ------------------------- | ---------------------------------------------------------------------- |
| Fund                      | Institutional investment funds                                         |
| Smart Trader              | Historically profitable traders; covers all 30D/90D/180D Smart Traders |
| 30D/90D/180D Smart Trader | Time-based performance labels; deprecated, use Smart Trader            |

#### Common Filters

| Filter Type   | Example                       |
| ------------- | ----------------------------- |
| Numeric Range | `{"min": 1000, "max": 50000}` |
| Integer Range | `{"min": 10, "max": 100}`     |
| Address List  | `["0x...", "0x..."]`          |
| Label List    | `["Fund", "Smart Trader"]`    |

#### Sort Order

```json
{
  "order_by": [
    {"field": "value_usd", "direction": "DESC"}
  ]
}
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.