> 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/11-11-2026-label-filters-require-premium-labels.md).

# 11-11-2026: Filtering or Sorting by Label Requires the Matching Label Tier

Requests that filter or sort by a label field now need access to the labels that field is matched against. A request that returns free-tier labels can no longer filter or sort by label text, because the match ran against premium labels the response does not show.

**Endpoints that need a paid plan and `premium_labels: true`** (billed at 150 credits per call):

| Endpoint                           | Label filter                   | Label sort |
| ---------------------------------- | ------------------------------ | ---------- |
| `/api/v1/tgm/holders`              | `filters.address_label`        | `name`     |
| `/api/v1/tgm/pnl-leaderboard`      | `filters.trader_address_label` |            |
| `/api/v1/tgm/perp-pnl-leaderboard` | `filters.trader_address_label` |            |
| `/api/v1/perp-leaderboard`         | `filters.trader_address_label` |            |

On these endpoints, a request that sends a label filter or sort without `premium_labels: true` returns HTTP 400, on every plan. Requests paid per request with x402 or MPP cannot use label filters or sorts on these endpoints, because `premium_labels: true` is not available with pay-per-request payment; they get the same HTTP 400 before any payment is taken. On `/api/v1/tgm/holders`, bitcoin requests are not affected.

**Endpoints that need a paid plan:**

| Endpoint                          | Label filter                                             | Label sort                               |
| --------------------------------- | -------------------------------------------------------- | ---------------------------------------- |
| `/api/v1/tgm/dex-trades`          | `filters.trader_address_label`                           | `trader_address_label`                   |
| `/api/v1/tgm/who-bought-sold`     | `filters.address_label`                                  |                                          |
| `/api/v1/tgm/perp-positions`      | `filters.address_label`                                  | `address_label`                          |
| `/api/v1/tgm/perp-trades`         | `filters.trader_address_label`                           |                                          |
| `/api/v1/tgm/transfers`           | `filters.from_address_label`, `filters.to_address_label` | `from_address_label`, `to_address_label` |
| `/api/v1/tgm/jup-dca`             | `filters.trader_label`                                   |                                          |
| `/api/v1/smart-money/dex-trades`  | `filters.trader_address_label`                           | `trader_address_label`                   |
| `/api/v1/smart-money/perp-trades` | `filters.trader_address_label`                           |                                          |
| `/api/v1/smart-money/dcas`        | `filters.trader_address_label`                           |                                          |

On these endpoints, requests from the Free plan that send a label filter or sort return HTTP 400.

**The error.** The response has `"code": "invalid_field_value"`, `"error": "LabelFilterNotAvailableError"`, and lists the refused fields in `invalid_filters` and `invalid_sort_fields`. These requests are not billed.

**What is not affected.** Requests without a label filter or sort work as before. A label filter set to an empty list (`[]`) is still accepted on every plan. Label category filters such as `include_smart_money_labels`, `exclude_smart_money_labels` and `label_type` work as before on every plan. Paid-plan requests that send `premium_labels: true` on the first four endpoints, and paid-plan requests on the other endpoints, are unchanged.


---

# 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/11-11-2026-label-filters-require-premium-labels.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.
