> ## Documentation Index
> Fetch the complete documentation index at: https://docs.o1.exchange/llms.txt
> Use this file to discover all available pages before exploring further.

# Data and AI access

> Public documentation, machine-readable launchpad configuration, onchain data, and safe wallet-based agent workflows.

o1 Launchpad documentation and production configuration are available in formats that work for people, search tools, coding agents, and other AI clients.

## Documentation resources

| Resource            | Access                                                   | Use                                                               |
| ------------------- | -------------------------------------------------------- | ----------------------------------------------------------------- |
| Documentation index | [Open `llms.txt`](https://docs.o1.exchange/llms.txt)     | Discover available documentation pages                            |
| Full documentation  | [Open full text](https://docs.o1.exchange/llms-full.txt) | Retrieve the public documentation as one text corpus              |
| Page Markdown       | Add `.md` to a documentation page URL                    | Retrieve clean context for one page                               |
| Skill description   | [Open `skill.md`](https://docs.o1.exchange/skill.md)     | Read the documentation's agent-facing capability summary          |
| Documentation MCP   | `https://docs.o1.exchange/mcp`                           | Connect an MCP client to search and retrieve public documentation |

<Note>
  The MCP URL is a client endpoint, not a web page. Opening it directly in a browser may return a method-not-allowed response.
</Note>

## Machine-readable production configuration

[`production-deployments.json`](/launchpad/reference/production-deployments.json) provides the current Base and Robinhood contract addresses, Uniswap dependencies, quote currencies, fees, opening settings, governance addresses, and contract caps.

The file is a dated public snapshot. Applications that prepare transactions should also read the current factory configuration before asking a wallet to sign.

## Public market and launch data

The o1 interface presents:

* launch discovery, search, newest tokens, market-cap ranking, trending, and 24-hour volume;
* token profiles, creators, socials, and explorer links;
* pool price, FDV, liquidity, charts, recent trades, and holders;
* immediate allocations and vesting schedules;
* creator announcements and token profile updates;
* creator, referral, platform, and vesting claim information.

Contract state and chain events are the authoritative sources for tokens, pools, trades, fees, claims, and vesting. The interface adds searchable and historical views around that public data.

## Safe agent workflow

<Steps>
  <Step title="Read current information">
    Retrieve the relevant documentation, production addresses, and live contract configuration.
  </Step>

  <Step title="Prepare an unsigned action">
    Build the launch, trade, or claim request with the selected chain, current fees, recipients, slippage, and deadline.
  </Step>

  <Step title="Show the complete result">
    Present the contract, assets, amounts, recipients, and expected outcome before requesting approval.
  </Step>

  <Step title="Sign with the user's wallet">
    The user reviews and signs in their wallet. Documentation and data tools never need the private key.
  </Step>
</Steps>

Agents and integrations should never store a private key, auto-sign transactions, or reuse a stale factory configuration.