> 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/integrations.md).

# Integrations — Wallets, Terminals & Bots

For wallets, terminals, trading bots and scanners. Five steps, end to end.

### 1. Connect

Robinhood Chain, chain id **`4663`**, RPC `https://rpc.mainnet.chain.robinhood.com`. Addresses: [Deployed contract addresses](/learn/tokenization-liquidity-and-onchain-systems/deployed-contract-addresses.md).

### 2. Discover agents

Watch one event on the Orbofi factories:

```solidity
event AgentCoinLaunched(
    address indexed asset, address indexed creator,
    address pool, address numeraire, uint256 initialSupply
);
```

It carries the token, creator, numeraire and supply in a single log. See [Index agent launches](/learn/tokenization-liquidity-and-onchain-systems/integrations/index-agent-launches.md).

### 3. Resolve the pool

Take the V4 pool id from the PoolManager's `Initialize` event in the same transaction. Every Orbofi pool has the same key shape — `fee 8388608`, `tickSpacing 200`, `hooks 0x4e3468…a544` — with only the currencies differing. See [Liquidity layer](/learn/tokenization-liquidity-and-onchain-systems/liquidity-layer.md).

### 4. Price it

`sqrtPriceX96` from `Initialize`, kept current from each `Swap`, converted through the numeraire's Chainlink feed. Market cap is price × total supply. See [Inspect an agent token](/learn/tokenization-liquidity-and-onchain-systems/integrations/inspect-an-agent-token.md).

### 5. Trade

Quote with `quoteExactInputSingle`, then execute through the Universal Router with Permit2. The fee is **dynamic** — always quote. See [Trade agent tokens](/learn/tokenization-liquidity-and-onchain-systems/integrations/trade-agent-tokens.md).

***

### What to know before you start

* **No bonding curve.** Tokens are in a Uniswap V4 pool from block one — no pre-DEX phase to model. (A gated migration path exists but has never fired; see the [FAQ](/learn/tokenization-liquidity-and-onchain-systems/faq.md).)
* **The token is a plain ERC-20** with no transfer tax. All fees are pool-side.
* **The first 10 seconds are expensive by design.** An 80% anti-snipe fee decays linearly to the standing rate. Quote, never hardcode.
* **The numeraire is not always WETH.** Stock-paired agents (NVDA, AAPL) are common.

{% hint style="info" %}
The August 2026 fee upgrade changed **only the factory address**. The token, pool key, router and quoter are unchanged, so existing integrations keep working once the new factory is in the allowlist.
{% endhint %}

***

## Verify your integration

Three commands that exercise the whole path. Run them against a public RPC before wiring anything up — if these work, your addresses and pool-key shape are right.

**1. Discovery — are launches visible?**

```bash
cast logs --address 0x8212F89CAFf7cB72E74008327983B52C909494FF \
  0x5d474dbccaef0b3274a2302f351854d215f5cb89d8d566861c19668c197670ad \
  --from-block 40680000 --rpc-url https://rpc.mainnet.chain.robinhood.com
```

Each hit is one agent. `topics[1]` is the token, `topics[2]` the creator.

**2. Quoting — is your pool key correct?**

Buying an agent with 0.001 WETH:

```bash
cast call 0x8dc178efb8111bb0973dd9d722ebeff267c98f94 \
  'quoteExactInputSingle(((address,address,uint24,int24,address),bool,uint128,bytes))(uint256,uint256)' \
  "((0x0bd7D308f8e1639FAb988Df18a8011f41eAcAd73,0xA197402dEA39E3D03c208319888bBD58976e6AAC,8388608,200,0x4e3468951D49f2EEa976eD0D6e75fFCb44a9a544),true,1000000000000000,0x)" \
  --rpc-url https://rpc.mainnet.chain.robinhood.com
```

Returns `amountOut` and a gas estimate. A revert here almost always means the pool key is wrong — most often a hardcoded `fee` (it must be `8388608`, the dynamic sentinel) or currencies in the wrong order.

**3. Pricing — does your maths agree with the pool?**

Quote the same pool in both directions. The buy and sell prices should straddle the price you derive from `sqrtPriceX96`, with a round-trip gap of roughly 3–4% — that is the swap fee each way plus slippage. If your derived price sits outside that bracket, the usual cause is inverting `tokenIsCurrency0`.

{% hint style="success" %}
A worked run of all three, on 2026-08-19: discovery returned 5 launches; the quote returned **463,453 agent tokens for 0.001 WETH**; the reverse returned **2.07e-6 WETH for 1,000 tokens**; and `sqrtPriceX96` gave 2.267e-9 WETH/token against quoted 2.158e-9 buy and 2.072e-9 sell. Consistent in both directions.
{% 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 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/integrations.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.