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	Discover available documentation pages
Full documentation	Open full text	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	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

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, Robinhood, Monad, Arc, BSC and X Layer contract addresses, staking deployments where supported, dated configuration, Uniswap dependencies, paired assets, fees, opening settings, governance addresses, and contract caps. The launch-contract-suites.json registry provides the current and historical launch suites for all six chains. Base, Robinhood, BSC and X Layer each share one factory across crypto and stock launches; Monad supports standard crypto launches, Arc uses ERC-20 USDC as its paired asset, and X Layer supports native OKB, USDC, xETH and 45 wrapped stocks. The current snapshot includes the exact eight registered Base crypto majors. The human-readable Stock-paired launches page lists the stock catalogs. The base-stock-quotes.json data file lists the ten registered Base Stock Tokens, while robinhood-stock-quotes.json lists all 194 registered Robinhood Stock Tokens.

These snapshots do not gate the application or Public API. Current creation availability comes from the shared platform catalog together with live quote registration and the active factory’s launch-enabled state. Historical-suite entries exist for attribution, indexing, trading, claims, vesting, and announcements; they must not be treated as current creation targets.

These JSON files are dated public snapshots that clients can fetch and parse directly. Resolve an existing token using its chain ID and originating factory rather than substituting the current factory. Applications that prepare new creation transactions should also read the current active 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.

The BSC stock catalog lists all 21 registered bStocks. Its native BNB, USDC and stock quotes use 18 decimals. BSC stock USD references use Binance data with USDT/USD and UI-multiplier normalization; crypto pricing uses the existing provider flow. Canonical launch/trade/fee events remain the source for indexed activity. A deployed catalog does not establish API availability or complete historical coverage.

X Layer entries include chain 196, native OKB, USDC, xETH and 45 wrapped stock quotes, the SwapX router and adapter, and the intended release governance configuration. Current quote registration and pending governance acceptance remain independently readable onchain. Native OKB uses 18 decimals. WOKB provides its same-chain pricing identity while the pool currency remains native OKB. The Public API’s supported chain list remains defined by its live /v1/config response.