# Token Utility

$HUNT is the native utility token that powers access, rewards, and alignment across the Greyhunt platform. Its role extends beyond gating premium features—serving as the foundation for both user privileges and contributor incentives.

{% tabs %}
{% tab title="Premium Access" %}

#### **Premium Access**

Users can unlock full feature access by either **staking $HUNT tokens** or subscribing via fiat. Premium users gain:

* Full visibility into all token dashboards (Deep‑Sense Signal)
* Expanded Bot‑Query allowances based on tier
* Configurable Smart Alerts with tier‑based slot limits
* Extended historical and comparative analytics
* Access to exclusive research and curated insights

Tier limits determine how many tokens can be monitored simultaneously and how many Bot Query interactions may be used each month: 

* Freemium: 3 Deep‑Sense tokens, 3 Smart Alerts, 5 Bot‑Query requests/month
* Basic: 10 Smart Alerts, 300 Bot‑Query requests/month
* Advance: 25 Smart Alerts, 600 Bot‑Query requests/month

Whether through staking or direct subscription, premium access provides a structured pathway for deeper analysis—allowing users to tailor the platform’s capabilities to their research needs.
{% endtab %}

{% tab title="Community Incentives" %}
Greyhunt is built around participatory intelligence. The platform will introduce **token-based incentives** to reward meaningful contributions, whether through discovery, validation, or the enrichment of signal quality.

Participation that supports signal quality or network utility may qualify for token-based rewards, with structures evolving as the ecosystem matures.
{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://greyhunt.gitbook.io/greyhunt-docs/tokenomics/token-utility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.