> 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/api/changelog/04-11-2026-nansen-score-retirement.md).

# 04-11-2026: Nansen Score retirement

Nansen Score top-token rankings retire and specific-token indicators keep four chains on December 4, 2026.

On **December 4, 2026**, Nansen will retire top-token rankings by Nansen Score and limit specific-token indicators to four chains across the API, MCP and CLI.

| API endpoint                           | Change on December 4, 2026                                                                                                      |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| `POST /api/v1/nansen-score/top-tokens` | Retires entirely. Requests will return an error instead of a token ranking.                                                     |
| `POST /api/v1/tgm/indicators`          | Remains available for `ethereum`, `solana`, `bnb` and `base`. Requests for other chains will return an unsupported-chain error. |

This is a 30-day customer notice and migration window beginning November 4, 2026. Existing requests remain supported until the applicable retirement date. The [separate chain retirement schedule](https://docs.nansen.ai/api/changelog/29-10-2026-chain-retirement.md) still applies: chains retiring globally on November 25 stop being available then, including on indicators. This notice does not extend those dates or remove chains from unrelated endpoints.

## Prepare your integration

* Remove calls to `/api/v1/nansen-score/top-tokens` from scheduled jobs and integrations before December 4. No equivalent score-ranking replacement is included in this change. Specific-token indicators do not replace a cross-token ranking.
* For `/api/v1/tgm/indicators`, keep requests only for `ethereum`, `solana`, `bnb` or `base`. Do not substitute a token's chain with another chain; remove unsupported-chain requests from your workflow.
* Update MCP prompts and tool calls that use `nansen_score_top_tokens` or `token_quant_scores`. Top-token discovery by Nansen Score will no longer be available; `token_quant_scores` will keep the four chains listed above.
* Update CLI jobs using `nansen research token top-tokens` or `nansen research token indicators`. The deprecated `nansen token ...` aliases are affected too. Changing clients or using an older client will not preserve access after retirement.

The indicators endpoint's response format and credit cost remain unchanged for the four retained chains. Requests for other chains will fail instead of silently returning an empty result or substituting a different chain. The endpoint itself is not being retired.

For help updating an integration, [contact Nansen support](https://support.nansen.ai/hc/en-us/requests/new).


---

# 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/api/changelog/04-11-2026-nansen-score-retirement.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.
