> 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/27-10-2026-holder-minimum-1-usd.md).

# 27-10-2026: Smart Money and Fund Holdings Count Holders Above $1

`holders_count` now counts a wallet when it holds more than $1 of the token. It used to require more than $100. This applies to:

* `POST /api/v1/smart-money/holdings`
* `POST /api/v1/smart-money/historical-token-balances`
* `POST /api/v1beta1/funds/holdings`

This matches `POST /api/v1/tgm/flows` and the Token God Mode holders chart, which already used $1.

Holder counts can rise because the counting rule changed. Wallets holding more than $1 and at most $100 now count. For example, on October 27 the Smart Money holder count for ETH on Ethereum was 311 under the old rule and 581 under the new one. Tokens whose only holders hold more than $1 and at most $100 now appear in results, so these endpoints return more tokens. `value_usd` and `share_of_holdings_percent` are unchanged, because they already included every balance.

If you filter or alert on `holders_count`, review your thresholds. Request formats and credit costs 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/27-10-2026-holder-minimum-1-usd.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.
