Skip to main content
Otto gives your agent market data, research and transaction tools. Start with the connection your application already supports. API schemas and examples explains how to inspect a request contract; service coverage compares the available interfaces.

Try a free catalog read

Add https://mcp.ottoai.services/mcp as a Streamable HTTP server in your MCP client’s connection settings. Then ask:
otto_catalog is free and needs no wallet. Next, try:
The first eligible cached intelligence result from a network address is free. Crypto news is paid-only and preserves that allowance; a shared network may already have used it. Other calls require a Base-USDC x402 payment; the MCP guide covers signing, receipts and retries. A generic MCP connection does not automatically supply a payment wallet. For a script you can run yourself, follow the terminal walkthrough: install the public packages, inspect tools, save a real response, handle a payment challenge and retry with the same authorization. It then connects to the separate unsigned-plan and verification example. The example client never loads a wallet key or submits a trade.

Choose a service

  • Market intelligence: news, token analysis, social context and yield screens.
  • AI tools: research and transaction explanations.
  • Data: tokenized stocks, SEC filings, web search and answers, X posts, token scores, prediction-market and real-world data.
  • Router: ask in plain words; it finds the right paid service or answers for one exact price.
  • Prepare and sign transactions: obtain an unsigned plan for your own signer.
Paying a service fee does not grant trading permission. A constructor signs nothing. Before you sign any transaction, identify the funded account, signer, recipient and exit path; the app’s connected wallet, Coinbase account and service accounts hold separate balances. Accounts & permissions explains those differences. If you want to use Otto directly without building an integration, open the app.