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

Documentation resources

ResourceAccessUse
Documentation indexOpen llms.txtDiscover available documentation pages
Full documentationOpen full textRetrieve the public documentation as one text corpus
Page MarkdownAdd .md to a documentation page URLRetrieve clean context for one page
Skill descriptionOpen skill.mdRead the documentation’s agent-facing capability summary
Documentation MCPhttps://docs.o1.exchange/mcpConnect an MCP client to search and retrieve public documentation
The MCP URL is a client endpoint, not a web page. Opening it directly in a browser may return a method-not-allowed response.

Machine-readable production configuration

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

1

Read current information

Retrieve the relevant documentation, production addresses, and live contract configuration.
2

Prepare an unsigned action

Build the launch, trade, or claim request with the selected chain, current fees, recipients, slippage, and deadline.
3

Show the complete result

Present the contract, assets, amounts, recipients, and expected outcome before requesting approval.
4

Sign with the user's wallet

The user reviews and signs in their wallet. Documentation and data tools never need the private key.
Agents and integrations should never store a private key, auto-sign transactions, or reuse a stale factory configuration.