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 file provides contract addresses, dated configuration, paired assets, fees, governance addresses and contract limits for the supported chains. The launch-contract-suites.json registry identifies current and historical deployments. See Stock-paired launches for supported assets, or use the machine-readable Base, Robinhood, BSC and X Layer stock lists. Standard and Tax use separate factories and paired-asset registrations. The Base Tax configuration, Robinhood Tax configuration, BSC Tax configuration, Monad Tax configuration, X Layer Tax configuration and Arc Tax configuration list each deployment’s contracts, percentage units, claim helper, quote registrations and Dividend exclusions. Use the hosted configuration to resolve a creation-available product route; currentSuiteIdsByProduct, where present, identifies the documented product selection. Resolve each Tax deployment by chain and suite, and use the originating factory to identify existing tokens. The JSON separates dated configuration observations from the documented releaseConfiguration; refresh mutable values from the selected Factory before building transactions. Arc native USDC uses 18 decimals while its shared ERC-20 view uses six; cirBTC uses eight. Resolve the originating suite and reward currency before interpreting event amounts. 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 entries preserve attribution and original contract bindings. Index-only Tax entries support indexing and direct recovery, not public preparation. Other historical suites retain their documented capabilities; none should be treated as the current creation target. 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. The Base and Robinhood $O launch snapshots identify each chain’s burn-only Factory, Hook, settlement reserve, adapter and wstO vault. Their percentage units and immediate quote burns are separate from Standard BPS fees and Tax reward allocations. Use launch_product=wsto for API configuration and preparation.

​
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;
  • Standard creator/referral/platform and Tax creator/protocol/integrator fee-claim information;
  • Tax dividend positions, trade-time reward assignment, holder-authorized claims, and burn collection versus delivery.
  • per-launch-pool wstO fee-burn totals, separate from global share supply, vault redemptions, reserve funds and recipient revenue.
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. Stock USD references use TickDB market data with the token’s onchain conversion applied once; crypto pricing uses Codex. Canonical launch/trade/fee events remain the source for indexed activity. A deployed catalog does not establish executable routes or complete historical coverage. X Layer entries include chain 196, native OKB, USDC, xETH and supported wrapped stocks, plus the SwapX router, adapter and release governance addresses. Read the factory for current settings before preparing transactions. 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.