> 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/guides/templates/complex-use-cases/use-case-6-finding-fomo-traders.md).

# Use case 6: Finding FOMO Traders

### 1. Scenario

Find the wallets that trade a token through the FOMO app, see how they trade it, and check whether a given wallet belongs to a FOMO user.

Nansen labels wallets that trade on the FOMO app with the trader's FOMO handle. Coverage includes Solana, Base and Robinhood, and grows as Nansen matches more wallets. These labels come through existing endpoints and fields. There is no FOMO-specific endpoint.

### 2. Solution

Use these endpoints. For what each call costs, see [Credits & Pricing](/getting-started/credits.md).

| Endpoint                                                             | Label field                              | FOMO label returned                |
| -------------------------------------------------------------------- | ---------------------------------------- | ---------------------------------- |
| [`tgm/dex-trades`](/api/token-god-mode/dex-trades.md)                | `trader_address_label`                   | By default                         |
| [`tgm/transfers`](/api/token-god-mode/token-transfers.md)            | `from_address_label`, `to_address_label` | By default                         |
| [`tgm/who-bought-sold`](/api/token-god-mode/who-bought-sold.md)      | `address_label`                          | By default                         |
| [`tgm/holders`](/api/token-god-mode/holders.md)                      | `address_label`                          | Only with `"premium_labels": true` |
| [`tgm/pnl-leaderboard`](/api/token-god-mode/pnl-leaderboard.md)      | `trader_address_label`                   | Only with `"premium_labels": true` |
| [`profiler/address/premium-labels`](/api/profiler/address-labels.md) | `label`, `category`, `kind`              | Always                             |

In Token God Mode responses, the label looks like this. It can start with other emoji when the wallet has more labels, for example `🔧 👀 "SKXonchain" on FOMO [8dppJhzr]`.

```
👀 "iganu" on FOMO [2k3jk299]
```

**Plan access:** FOMO labels are premium labels.

* In Token God Mode responses, only paid plans see them. On the Free plan, the label fields leave out the FOMO handle and show the wallet's other label, or an empty string if it has none.
* `"premium_labels": true` on `tgm/holders` and `tgm/pnl-leaderboard` requires a paid plan. See [Premium Labels Default Change](/api/changelog/17-07-2026-premium-labels-default-change-live.md).
* `profiler/address/premium-labels` returns FOMO labels on every plan.

### 3. Step-by-Step Guide

The examples read your API key from the `NANSEN_API_KEY` environment variable. Set it before running them.

#### Step 1: Find FOMO traders on a token

Pass the pattern `%on FOMO%` to the label filter to return only FOMO traders:

```bash
curl -X POST "https://api.nansen.ai/api/v1/tgm/dex-trades" \
  -H "apikey: $NANSEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain": "solana",
    "token_address": "5THtNEGTF1y67eRWvcgz3MomDZePCVx1xdskHHeCpump",
    "date": {"from": "2026-09-01T00:00:00Z", "to": "2026-10-01T23:59:59Z"},
    "filters": {"trader_address_label": "%on FOMO%"},
    "pagination": {"page": 1, "per_page": 100}
  }'
```

**Process the response:**

* Each row is one trade. `trader_address` is the wallet, and `trader_address_label` carries the FOMO handle.
* Group by `trader_address` to get each FOMO trader's buys and sells.

The same pattern works on `from_address_label` and `to_address_label` in `tgm/transfers`.

#### Step 2: Rank FOMO traders by PnL

Add `"premium_labels": true`, then filter on `trader_address_label`:

```bash
curl -X POST "https://api.nansen.ai/api/v1/tgm/pnl-leaderboard" \
  -H "apikey: $NANSEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain": "solana",
    "token_address": "5THtNEGTF1y67eRWvcgz3MomDZePCVx1xdskHHeCpump",
    "date": {"from": "2026-09-01T00:00:00Z", "to": "2026-10-01T23:59:59Z"},
    "premium_labels": true,
    "filters": {"trader_address_label": "%on FOMO%"},
    "pagination": {"page": 1, "per_page": 100}
  }'
```

To see which FOMO traders still hold the token, call `tgm/holders` with `"premium_labels": true` and `"filters": {"address_label": "%on FOMO%"}`. Leave out `date`: holders returns current balances, and a request with `date` fails with HTTP 422. Like `tgm/pnl-leaderboard`, it costs more with `premium_labels`.

#### Step 3: Check a single wallet

```bash
curl -X POST "https://api.nansen.ai/api/v1/profiler/address/premium-labels" \
  -H "apikey: $NANSEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain": "solana",
    "address": "2k3jk29928ReKRuTC9QDRBj3smoM9PBv7nKhstoURwxB"
  }'
```

A FOMO wallet returns two labels:

```json
{
  "data": [
    {"label": "\"iganu\" on FOMO", "category": "social", "kind": ["unique-identifier/fomo-trader"]},
    {"label": "👀 \"iganu\" on FOMO", "category": "others", "kind": []}
  ]
}
```

**Process the response:** the wallet is a FOMO trader if any label has `unique-identifier/fomo-trader` in `kind`. Don't match on the label text. It is display text, and its format varies, for example with extra emoji.

### 4. Limits

* `profiler/address/premium-labels` costs much more per call than the Token God Mode endpoints. Use it for single-wallet checks, and use the Token God Mode endpoints to find FOMO traders in bulk.
* `profiler/address/labels` doesn't return FOMO labels.
* On `tgm/who-bought-sold`, the `address_label` filter with `%on FOMO%` can time out on busy tokens. Fetch the rows without it and filter `address_label` in your own code.


---

# 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/guides/templates/complex-use-cases/use-case-6-finding-fomo-traders.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.