otto

Install / Bring your own agent

Otto, in your workflow.

Connect your assistant, use Otto’s npm tools or call an endpoint directly. Pick the runtime and payment network that fit your workflow.

Read the docs

Choose your setup

No Otto Wallet required for these setup paths. Use the payment flow of your chosen runtime.

Otto MCP

Otto intelligence, in your assistant.

Connect to Otto’s own hosted MCP for market intelligence and unsigned transaction construction. Your client handles tool discovery and payment requests. A prepared transaction still needs a separate signing and submission step.

  1. Add https://mcp.ottoai.services as a remote MCP server.

  2. Discover the tools your client can use, then ask for market or company context.

  3. Read the tool’s payment request. Paid intelligence uses USDC on Base; a first-call allowance may apply.

Hosted Otto MCP and local alternative
# Hosted Otto MCP — add this URL in your MCP client's remote-server settings:
https://mcp.ottoai.services

# Claude Code:
claude mcp add otto-intel --transport http https://mcp.ottoai.services

# Local alternative (intelligence tools; Node 22+):
# Configure X402_PRIVATE_KEY in your MCP client's secret environment first.
# Local calls can automatically spend that wallet's USDC on Base.
npx -y otto-intel-mcp@0.1.3

# Hosted and local tool catalogs differ. Check the docs before choosing.

Hosted MCP · Payment-capable client required after any free allowance

Read Otto MCP setup

Otto’s own packages

Build it into your workflow.

Published on npm · versioned commands you can inspect before running.

otto-intel-mcp v0.1.3

Run intelligence locally

Local MCP intelligence tools, paid from a wallet you configure. The hosted server has additional tools; installing this package does not reproduce its full catalog.

Install otto-intel-mcp
npm install otto-intel-mcp@0.1.3

Node 22+ · npm 10+ · Configure X402_PRIVATE_KEY in your client’s secret environment

Setup and capabilities
otto-execute v0.1.3

Verify before you sign

A CLI and library for checking an Otto execution artifact against your own intent. The published quickstart covers Base swaps; signing, submission and any delegated path have separate requirements.

Install otto-execute
npm install otto-execute@0.1.3

Node 22+ · Verification needs no private key · Submission moves funds

Setup and capabilities

x402 payment networks

Same idea. Different ways to pay.

A storefront’s payment network does not define where it can trade or what data it covers.

Base mainnet · 8453

Base

USDC

The main Otto endpoint catalog. Some requests also offer USDC on Solana; only choose that alternative when it appears in the live challenge and your client supports it.

Client fit

EVM x402 client for Base; SVM support for a Solana alternative.

X Layer mainnet · 196

X Layer

USDT0 · USDC · USDG

Otto X has its own endpoint catalog and OKX payment integration. It includes intelligence, recipes and separate execution offerings; it is not a copy of the Base catalog.

Client fit

An OKX-compatible exact-payment client. Aggregated deferred payments additionally require the Agentic Wallet setup.

Algorand MainNet

Algorand

USDC · ASA 31566704

A read-only Otto catalog with Algorand settlement through GoPlausible. This storefront exposes GET data routes; it does not expose trading or other fund-moving POST routes.

Client fit

An AVM-capable x402 client and an Algorand USDC account. An EVM-only signer cannot pay this rail.

Package versions and public payment challenges checked . Check the live response for this request’s price, accepted asset and network. These setup checks did not make a paid call.

More autonomous workflows

Know what’s ready.
Follow what’s next.

Bring-your-own-agent access and autonomous payment permissions have different readiness and funding requirements.

Get runtime updates

Choose what you want to hear about.

Which runtime are you waiting on?

EAL · CLAUDE CODE / CURSOR

BYO access available

Empire Access Layer

Bring your own agent using the quickstart. Fund-one-Safe auto-pay remains disabled pending funded proof and review.

Access, funding and permissions

Your own Claude Code or Cursor calls the whole empire — x402 intelligence, swaps, yield — paid per call in USDC. The BYO half is live today: hand one block to your agent and it sets up a throwaway wallet and makes the first paid call itself — you just send the USDC. Fund-one-Safe auto-pay reuses Otto’s permission pair — a general trading permission plus a bounded billing one, each ending at its own expiry or your revocation, whichever comes first — and remains disabled pending its funded proof and review.

Agent quickstart

HERMES

Building

Autonomous Routing

Hermes routes agentic intent across Otto's surfaces and external runtimes — picks the cheapest live channel per call and pays in USDC. Building.