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

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

The production-deployments.json data file provides the current Base and Robinhood launch-suite addresses, staking deployments, dated availability state, Uniswap dependencies, paired assets, fees, opening settings, governance addresses, and contract caps. The human-readable Stock-paired launches page lists both stock catalogs. The base-stock-quotes.json data file lists the four registered Base Stock Tokens, while robinhood-stock-quotes.json lists all 194 registered Robinhood Stock Tokens. The snapshot does not gate the application or Public API. Current creation availability comes from the shared platform catalog together with live quote registration and the factory’s launch-enabled state. These JSON files are dated public snapshots that clients can fetch and parse directly. 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 across All, Crypto, and Stocks views, global search, newest tokens, liquidity, trending, and 24-hour volume;
  • token profiles, creators, socials, and explorer links;
  • pool price, FDV, liquidity, charts, recent trades, and holders;
  • creator announcements and token profile updates;
  • creator, referral, and platform fee-claim information.
Contract state and chain events are the authoritative sources for tokens, pools, trades, fees, and claims. 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, creation route, paired asset, 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, reuse a stale factory configuration, or infer a creation route from a token symbol alone.