Get real-time statistics of Hyperliquid wallets grouped into tiers by PnL size, 8 tiers from Money_Printer to Giga_Rekt, including address counts, long and short position values and shares, long/short sentiment, and the distribution of profitable and losing addresses.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Available on these API plans: Standard Professional Enterprise
Response Data
data is an array; each element is one PnL tier. group_name is the tier tag in lowercase: money_printer | smart_money | grinder | humble_earner | exit_liquidity | semi_rekt | full_rekt | giga_rekt. minimum_amount and maximum_amount are the tier's PnL amount range (in USD); for example, smart_money is 100000–1000000, and money_printer has a lower bound of 1000000 and no upper bound. Loss tiers run the other way: minimum_amount is the end with the smaller loss and maximum_amount the end with the larger loss, e.g., -100000 to -1000000 for full_rekt, while giga_rekt has only minimum_amount (-1000000), meaning a loss of $1 million or more. This endpoint has no request parameters.
Share Fields Are Already Percentage ValuesThe
*_percentfields are in %:72.46means 72.46%; there is no need to multiply by 100.
200 · application/json · See the response example in the right panel.
| Field | Type | Always Returned | Description |
|---|---|---|---|
code | string | Yes | Business status code; "0" means success |
msg | string | No | Result message; may be omitted on success |
data | array of object | Yes | Statistics by PnL amount tier; each element is one tier |
data[].group_name | string | Yes | Tier tag, lowercase; for the possible values, see the description above |
data[].all_address_count | integer | Yes | Total number of addresses tracked in the tier |
data[].position_address_count | integer | Yes | Number of these addresses that currently hold positions |
data[].position_address_percent | number | Yes | Addresses with positions as a share of the tier's total addresses, in % |
data[].bias_score | number | Yes | Long/short bias score; positive values correspond to a bullish bias_remark, negative values to a bearish one; the larger the absolute value, the more pronounced the bias |
data[].bias_remark | string | Yes | Long/short sentiment label; values seen so far: very_bearish, bearish, slightly_bearish, indecisive, slightly_bullish, bullish, very_bullish |
data[].minimum_amount | number | Yes | Start of the tier's PnL range, in USD. For profit tiers it is the smaller end, and for loss tiers it is the end with the smaller loss, e.g., -100000 for full_rekt |
data[].maximum_amount | number | No | End of the tier's PnL range, in USD. For profit tiers it is the larger end, and for loss tiers it is the end with the larger loss, e.g., -1000000 for full_rekt; not returned for the two outermost tiers, money_printer and giga_rekt |
data[].long_position_usd | number | Yes | Long position value of the tier, in USD |
data[].short_position_usd | number | Yes | Short position value of the tier, in USD |
data[].long_position_usd_percent | number | Yes | Share of long position value, in % |
data[].short_position_usd_percent | number | Yes | Share of short position value, in % |
data[].position_usd | number | Yes | Total position value of the tier (long + short), in USD |
data[].profit_address_count | integer | Yes | Number of profitable addresses |
data[].loss_address_count | integer | Yes | Number of losing addresses |
data[].profit_address_percent | number | Yes | Share of profitable addresses, in % |
data[].loss_address_percent | number | Yes | Share of losing addresses, in % |
API Plans
Only the API plans marked Yes in the table below can call this endpoint. For the price of each plan, see API Plans.
| API Plan | Access |
|---|---|
| Hobbyist | ❌ No |
| Startup | ❌ No |
| Standard | ✅ Yes |
| Professional | ✅ Yes |
| Enterprise | ✅ Yes |
Use This Endpoint with AI
Pick a task and click Open in ChatGPT or Open in Claude: the AI reads this page first and then gives you the result. You can also click Copy and paste the full prompt into the AI tool you use.
This endpoint provides data through the REST API. Use the prompts above to have AI write the request code. For the tools available through MCP, see CoinGlass MCP.
Use Cases
| Scenario | Description |
|---|---|
| Follow Smart Money | Watch the long/short direction of consistently profitable wallets such as Money_Printer and Smart_Money. |
| Contrarian Reference | Watch the direction of the wallets that have lost the most, such as Full_Rekt and Giga_Rekt, as a contrarian sentiment reference. |
| Sentiment Dashboard | Turn the bias_remark and long/short shares of the 8 tiers into a dashboard to see at a glance which side the winners and the losers are betting on. |
| Combine with Historical Data | If you need the historical changes of a tier, use Hyperliquid Position Distribution (by Tag). |
Related Endpoints
| Endpoint | How It Differs |
|---|---|
| Hyperliquid Wallet Position Distribution | Tiers by position size, with the same fields |
| Hyperliquid Position Distribution (by Tag) | Historical data for one tier |
| Hyperliquid Long/Short Account Ratio (by Tag) | History of long and short account counts for one tier on a given coin |
| Hyperliquid Whale Positions | Position-by-position details of large positions |
FAQ
Does a percentage field value of 55.32 mean 55.32%?
Yes. All *_percent fields of this endpoint are already percentage values: 55.32 means 55.32%; there is no need to multiply by 100.
Why do some tiers have no maximum_amount?
The two outermost tiers do not return this field: the most profitable tier, money_printer (minimum_amount of 1000000, i.e., a profit of $1 million or more), and the tier with the largest losses, giga_rekt (minimum_amount of -1000000, i.e., a loss of $1 million or more). Check whether the field exists before reading it; for loss tiers, do not apply “minimum ≤ PnL ≤ maximum” but read the bounds by absolute value.
How is it different from Hyperliquid Wallet Position Distribution?
The returned fields are exactly the same; the difference is what the tiers are based on: this endpoint groups by PnL amount, while Hyperliquid Wallet Position Distribution groups by position size.
Is group_name uppercase or lowercase?
It is actually returned in lowercase, e.g., money_printer, giga_rekt. When calling the endpoint that queries history by tag, the docs for the wallet_tag parameter write the values with initial capitals, e.g., Money_Printer.
Learn More: Hyperliquid Wallet PnL Tiers
What Do Money_Printer, Smart_Money and Giga_Rekt Mean?
These are names given to wallets by PnL amount. The profitable tiers, from highest to lowest, are Money_Printer, Smart_Money, Grinder and Humble_Earner; the losing tiers are Exit_Liquidity, Semi_Rekt, Full_Rekt and Giga_Rekt. Rekt is crypto slang for “lost badly”.
Why Look at the Direction of Profitable Wallets?
Consistently profitable wallets tend to have more trading experience, and their collective direction can serve as a reference for market sentiment, but past profits do not mean they are necessarily right this time.
Can PnL Tiers and Position Tiers Be Viewed Together?
Yes. Looking at this endpoint together with Hyperliquid Wallet Position Distribution lets you tell whether the two groups, those with “large positions” and those who “earn the most”, agree.
