Skip to main content
Otto AI services are accessible through multiple channels, each optimized for different use cases. This guide helps you choose the right path. For custody, funding, permissions, and recovery behavior across rails, use the Web3 Operating Manual.

Quick Comparison


Option 1: Otto AI DApp

Best for: End users who want a guided web interface with form-driven DeFi mini-agents.

What You Get

The Otto AI DApp is the primary user-facing product: a Next.js web app whose front door is /app Mission Control — a dashboard with mini-agents, market views, and portfolio workflows backed by one Safe smart account. For deterministic machine-to-machine access, use ACP, x402, MPP, USDC Gateway, or Otto X directly.
  • Mini-Agents — focused, form-driven workflows for swaps, bridges, DCA, and RSI: pick the mini-agent, enter tokens/amounts/leverage, review, and confirm. Every on-chain action requires explicit confirmation.
  • Market Insights — live dashboard with 9 sections: daily briefing, market pulse, trending tokens, news, yields, movers, KOL sentiment, Twitter digest, and derivatives data.
  • Portfolio Co-Pilot — connect your wallet for a portfolio overview plus a single display-only suggestion that links idle USDC to the top live, deployable yield venue. It never executes; you review and approve every deposit.

Quick Start

  1. Visit useotto.xyz
  2. Connect your wallet (browser extension or email sign-up)
  3. Open /app Mission Control and pick a mini-agent — enter the amount and confirm

Pricing

  • $OTTO holders (50K+): Unlimited daily usage
  • Free tier: Daily usage cap with no payment required

Option 2: ACP (via acp-cli or the ACP Web GUI)

Best for: Developers + AI agent operators who want on-chain USDC escrow, signed receipts, and ERC-8004 reputation. The Agent Commerce Protocol (ACP) is Virtuals’ decentralized marketplace for AI agent services. Install @virtuals-protocol/acp-cli and call Otto’s four agents directly — see the acp-cli quickstart for the end-to-end flow — or use the ACP Web GUI (search “Otto AI”, submit jobs).
Butler is deprecated. The Twitter/Web-GUI middleman that routed user requests to Otto’s agents is no longer the canonical path — use acp-cli or the ACP Web GUI. The legacy @Butler_agent relay is preserved for historical context only and is not maintained.
Otto’s agent architecture — escrowed fund transfers, evaluator-based job completion, and gasless smart-account execution — is ERC-8183 (Agentic Commerce)-ready. ACP jobs are priced in USDC; see the individual agent pages (Market Alpha, Trade Execution, Tools, Prediction Markets).

Option 3: Otto x402 Storefront

Best for: Developers and AI agents who want fast, programmatic access with micropayments.

How It Works

The x402 V2 protocol enables pay-per-request API access using the HTTP 402 status code. No API keys or registration required — pay with USDC on Base, Polygon, or Solana.

Quick Start

  1. Fund a wallet with USDC on Base, Polygon, or Solana
  2. Use the @x402/axios V2 client library
  3. Make requests to https://x402.ottoai.services

x402 V2 Features

  • SIWX: Pay once for data endpoints, re-access free for 1 hour with wallet signature
  • Signed Receipts: Cryptographic proof of service delivery (EIP-712) on every call
  • Bazaar Discovery: Read-only endpoints discoverable by AI agents on CDP Bazaar
  • Permit2 Ready: Infrastructure supports any ERC-20 token — contact us for custom integrations

Pricing

All prices in USDC. Example endpoints: Storefront docs: Otto x402 Storefront

Option 4: Otto MPP Storefront

Best for: Tempo/Stripe clients that need paid reads and query tools without principal movement. MPP exposes Otto’s blessed read-only/query catalog: Market Alpha reads, AI research and creative query endpoints, and wallet-scoped trading resources. It intentionally does not expose swaps, bridges, deposits, withdrawals, Hyperliquid order execution, or any other principal-moving POST route. Storefront docs: Otto MPP Storefront

Option 5: Otto USDC Storefront

Best for: High-frequency agents that want gas-free paid reads funded by Circle Gateway USDC. The USDC Gateway surface is a compact read subset for agents that already keep funds in a GatewayWallet. It is not a replacement for x402 execution or ACP jobs. Storefront docs: Otto USDC Storefront

Option 6: Otto X Storefront

Best for: X Layer users and agents that want OKX Onchain OS integrations, X Layer-native payment, or autonomous sub-wallet execution. Otto X has its own catalog: market intelligence, AI tools, X Layer DEX reads, TEE-custodied sub-wallet execution, Yield Copilot, and Yield Watch. It overlaps with the main swarm but is not a one-for-one mirror of x402 or MPP. Storefront docs: Otto X Storefront

Option 7: OpenClaw Skills

Best for: AI agents using the OpenClaw framework who want pre-built skill integrations.

What is OpenClaw?

OpenClaw is a popular framework for building AI agents. Otto AI provides skill files that enable OpenClaw agents to access our services.

Two Approaches

A. Our OpenClaw Skills (x402-based)

Pre-built skills for direct x402 API access to Otto AI services. Repository: github.com/useOttoAI/openclaw-skills Available Skills: Installation:

B. Virtuals OpenClaw ACP (Generic ACP Access)

Virtuals provides an official OpenClaw integration for accessing ANY ACP agent, including Otto AI. Repository: github.com/Virtual-Protocol/openclaw-acp Tools Provided:
  • browse_agents - Discover ACP agents
  • execute_acp_job - Submit jobs to any agent
  • poll_job - Check job status
  • get_wallet_balance - Check agent assets
Use this if: You want your agent to discover and use multiple ACP agents dynamically.

Option 8: Marketplaces & Mini Apps

Otto AI is also listed on third-party agent marketplaces and platforms for broader discovery.

Moltlaunch

Otto AI agents are listed on the Moltlaunch agent marketplace, expanding discoverability within the AI agent ecosystem.

Base Mini App

Otto AI is available as a Base Mini App within the Farcaster ecosystem, providing access directly from the Base social layer.

Option 9: Base MCP

Best for: Anyone running an AI assistant (Claude, ChatGPT, Cursor, Codex) with a Base Account who wants to bring Otto’s intelligence into their existing chat.

What You Get

Base MCP connects your Base Account to your AI assistant and can pay any x402-enabled service. Otto’s services are live x402 endpoints with USDC on Base — so your assistant can call Otto’s market alpha, KOL sentiment, yield discovery, token security, and AI research and settle each call from your Base Account. You approve and pay per call. This is the interactive path: you drive Otto, you approve each move. Otto’s Base MCP skill deliberately exposes read-only intelligence and research only — not swaps or perps — because paying an x402 endpoint signs a payment, not the underlying trade. Act on Otto’s intelligence with your wallet’s own tools, or step up to Otto autonomy for bounded set-and-forget delegation.

Quick Start

  1. Install Base MCP in your assistant: docs.base.org/ai-agents/quickstart
  2. Point it at Otto’s skill: https://x402.ottoai.services/otto.md
  3. Ask for alpha — e.g. “What’s the top USDC yield on Base right now?” — and approve the small USDC payment in your Base Account.
Machine-readable catalog: https://x402.ottoai.services/otto-x402-catalog.json

Which Should I Choose?

Use the DApp. Guided web interface — /app Mission Control with form-driven mini-agents, dashboards, and portfolio tools. No payment required for the free tier.

Feature Availability by Channel

For the authoritative, source-generated capability matrix across DApp, ACP, x402, MPP, USDC Gateway, and Otto X, see Access Paths & Coverage — it is generated from storefront source and stays tied to code, so it does not drift the way a hand-maintained table does.
DApp availability can be a guided product workflow rather than a one-for-one machine endpoint. Agent builders should treat the storefront discovery docs as the source of truth for programmatic access. OpenClaw skill coverage is on the OpenClaw option above.

Support

Need help choosing or getting started?