> For the complete documentation index, see [llms.txt](https://docs.hatchr.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatchr.fun/hatch/hatch-token.md).

# HATCH Native Token

Hatchr plans to launch its native token, **HATCH**, once the Hatchr application is live.

## Current status

At the date of these docs:

* no HATCH contract address is published here;
* no final supply is announced here;
* no allocation or vesting schedule is announced here;
* no sale terms are announced here; and
* no final utility commitments are announced here.

This is deliberate. Hatchr will publish tokenomics only after the HATCH contracts and parameters are final.

## How to verify the announcement

The official HATCH contract address and finalized token information will be announced through all three channels:

1. [hatchr.fun](https://hatchr.fun)
2. [x.com/hatchr\_rh](https://x.com/hatchr_rh)
3. [t.me/hatch\_rh](https://t.me/hatch_rh)

Cross-check the address on the Robinhood Chain explorer before interacting.

{% hint style="danger" %}
Until Hatchr publishes an address through its official channels, any token using the HATCH name or ticker should be treated as unofficial.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.hatchr.fun/hatch/hatch-token.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.