# Tokenomic

<figure><img src="/files/OFiXC9PQfbmVSACwmZL1" alt=""><figcaption></figcaption></figure>

AMI Tokenomics Overview

The AMI token is designed to support a sustainable and balanced ecosystem, with a total supply of 1,000,000,000 tokens, allocated across the following categories:

* **Seed Round**: 120,000,000 AMI (12.00%) – Early-stage funding to support project development.
* **Private Sale**: 30,000,000 AMI (3.00%) – Exclusive investment opportunities for select investors.
* **KOL**: 10,000,000 AMI (1.00%) – Exclusive investment opportunities for influencers.
* **Liquidity**: 50,000,000 AMI (5.00%) – Reserved for trading activities on CEX and DEX.
* **Community Rewards**: 200,000,000 AMI (20.00%) – Incentivizes the usage of Amnis’ current and future core products.
* **Marketing**: 150,000,000 AMI (15.00%) – Dedicated to incentive programs and future activities to acquire and retain users.
* **Ecosystem**: 160,000,000 AMI (16.00%) – Set aside for grants, partnerships, and other ecosystem initiatives.
* **Team**: 200,000,000 AMI (20.00%) – Allocated to the core team for long-term commitment.
* **Airdrop**: 80,000,000 AMI (8.00%) – Rewarded to early adopters and earmarked for future distributions.

This well-balanced allocation ensures growth, stability, and engagement within the AMI ecosystem.

## **API Endpoint**

**Total Supply:**
\
<https://api.amnis.finance/api/v1/ami/total-supply> <br>

**Circulating Supply:** \
<https://api.amnis.finance/api/v1/ami/**circulating**-supply>


---

# 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://docs.amnis.finance/ami-token/tokenomic.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.