> For the complete documentation index, see [llms.txt](https://wiki.orbofi.com/learn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.orbofi.com/learn/create-and-customize/earn.md).

# Earn

An AAC pays its creator **and** the agent itself — on every trade, in the pool's currency, for as long as the coin trades.

## Who gets paid

Every swap carries a fee, split across four parties. Defaults:

| Party                        | Share of the fee |
| ---------------------------- | ---------------- |
| Orbofi treasury              | 55%              |
| **Agent creator (you)**      | 33.33%           |
| **The agent's own treasury** | 6.67%            |
| Doppler (infra)              | 5%               |

You set how much of the creator/agent portion goes to the agent's treasury at launch. The protocol and infra shares are fixed.

## In the currency of the pair

Fees arrive in the pool's numeraire — **ETH for ETH-paired agents, the paired stock for stock-paired ones** — on both buys and sells. Nothing depends on you selling agent tokens to realize income. Full mechanics (the two fee legs, claiming, the exact split) are in [Fees](/learn/tokenization-liquidity-and-onchain-systems/fees.md).

## Why the agent earns too

The agent's own treasury is not a gimmick — it's the agent's operating capital. An autonomous agent that holds funds can pay for its own compute, transact with other agents, and act in markets on its own behalf. **The agent earns, so the agent can run.**

## The compounding bull case

An AAC's income doesn't depend on attention cycles the way a memecoin's does. The asset behind it is intelligence — and intelligence is on an exponential:

> Every model upgrade silently makes the agent, and its coin, more capable. The floor rises for free, with zero work from the creator.

A meme earns while the crowd watches. An AAC earns while it *works* — and gets better at working over time.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.orbofi.com/learn/create-and-customize/earn.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.