> For the complete documentation index, see [llms.txt](https://aesoperator.gitbook.io/aesoperator/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aesoperator.gitbook.io/aesoperator/roadmap/tokenomics.md).

# Tokenomics

## ACT I: $AESOP

* Total supply: 1,000,000,000 (1 billion) AESOP tokens
* 89.87% burned and locked in LP ([Verify on Rugcheck](https://rugcheck.xyz/tokens/CpEpquNgiGyeMeTBrJJCgMXL8vn1jCkWKVbSurhJpump))
* 0.7% team allocation locked until February 28th, 2025([Verify on Streamflow](https://app.streamflow.finance/contract/solana/mainnet/HCym2tDaV1eZFkfpBns6RABKufVcbmXxFApg9jPkiweY))
* Team (of 2 currrently) holds minimal tokens which ensured fair launch

## Access Passes

Access passes are our main way of raising funds to develop and operate Aesoperator ACT 1:

* Maximum supply: 5555
* Duration: 6 months access, converting to pay-per-hour after
* Price: 2.22 SOL per pass

### Treasury & Operations

* Treasury wallet: GvBQMHcP2BmtQjR5pHr5Vij4qV1tvpEy47HGmUhbN1ea
* Monthly operational costs
  * H100 GPUs
  * OpenRouter API access
  * Infrastructure and hosting
* Token allocation secured via [Streamflow contract](https://app.streamflow.finance/contract/solana/mainnet/HCym2tDaV1eZFkfpBns6RABKufVcbmXxFApg9jPkiweY)

## Utility

Pay-per-hour Model

* 10,000 AESOP per hour as compute costs scale with more complex reasoning
* ACT 2

## Fund Usage

* Acquisitions of projects and teams
* Infrastructure costs (GPUs, APIs, hosting)
* Development team
* Bug bounties
* Operations and maintenance
* Platform improvements
* Community incentives

Note: We haven't raised funds through $AESOP. All funding comes through access pass sales to support aquiring other projects and teams and development costs. We see aquisitions as a way to buy distribution to the Aesoperator project.


---

# 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://aesoperator.gitbook.io/aesoperator/roadmap/tokenomics.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.