Skip to main content
Otto gives your agent market data, research, generated media and transaction tools. Start with the connection your application already supports. The interfaces have different catalogs and account requirements. API schemas and examples explains how to inspect the current 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

Paying a service fee does not grant trading permission. A constructor signs nothing. Before an execution call, 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.