> 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/tokenization-liquidity-and-onchain-systems/developers.md).

# Overview

Orbofi is a launchpad for **autonomous agent coins** — standard ERC-20s tradable on **Uniswap V4**, with an AI agent's intelligence embedded behind each one — live on [Robinhood Chain](https://chain.robinhood.com) (chain id **4663**).

### How the on-chain system works

```
creator → Orbofi Factory → Doppler Airlock → ERC-20 + Uniswap V4 pool
                                                    ↓
                                            trades immediately
```

Four things are worth knowing up front, because they differ from most launchpads:

* **No bonding curve.** The token goes straight into a Uniswap V4 pool at launch and trades there from block one.
* **No graduation.** There is no threshold, no migration and no second venue. Liquidity is in V4 from the start and stays there.
* **The token is a plain ERC-20.** No transfer tax, no rebasing, no blacklist. All fees are charged by the pool, not the token.
* **Liquidity is locked.** The launch position is not withdrawable by the creator.

### Sections

| Section                                                                                                         | Contents                                                |
| --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| [Tokenization](/learn/tokenization-liquidity-and-onchain-systems/tokenization.md)                               | The factory, the token, what happens at launch          |
| [Liquidity layer](/learn/tokenization-liquidity-and-onchain-systems/liquidity-layer.md)                         | The V4 pool, the anti-snipe window, pricing             |
| [Fees](/learn/tokenization-liquidity-and-onchain-systems/fees.md)                                               | The fee model, and the one field that misleads indexers |
| [Integrations](/learn/tokenization-liquidity-and-onchain-systems/integrations.md)                               | Wallets, terminals, bots and scanners                   |
| [Deployed contract addresses](/learn/tokenization-liquidity-and-onchain-systems/deployed-contract-addresses.md) | Every address, verified on chain                        |
| [ABIs](/learn/tokenization-liquidity-and-onchain-systems/abis.md)                                               | Events and methods for parsing                          |
| [FAQ](/learn/tokenization-liquidity-and-onchain-systems/faq.md)                                                 | Common integrator questions, answered directly          |

### Fastest path for a wallet or terminal

Watch one event on the Orbofi factory:

```solidity
event AgentCoinLaunched(
    address indexed asset,   // the agent's ERC-20
    address indexed creator,
    address pool,
    address numeraire,       // WETH or a tokenized stock
    uint256 initialSupply
);
```

That is the whole discovery step. Details in [Index agent launches](/learn/tokenization-liquidity-and-onchain-systems/integrations/index-agent-launches.md).


---

# 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/tokenization-liquidity-and-onchain-systems/developers.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.