Agent Toolings

Bring transaction capability to your existing agent stack

Connect coding agents through Skills, hosted MCP, or the CLI. Three surfaces, one account-owned execution lifecycle.

Choose a surfaceRead the docs

Choose your surface

Start with a compatible interface with flexibility.

These entry points share execution infrastructure, but they solve different setup, session, and signing problems.

Agent Skills

01

Teach Codex, Claude Code, or Cursor the correct Aomi workflow before the agent touches a transaction.

Best forGuided trading and App-building workflows
Install Skills

Hosted MCP

02

Connect any supported MCP client to account-owned Aomi sessions through browser OAuth.

Best forHosted conversations with almost no local setup
Connect MCP

Client CLI

03

Work directly with chat, sessions, simulation, and signing from the terminal you already operate.

Best forOperators, scripting, and local wallet control
Install CLI

Aomi execution harness

  • One Aomi account
  • Policy enforced outside the model
  • Sessions resumable across surfaces
Simulaterehearsed on a fork
Signyour wallet, never Aomi
Benchmarked on AomiBench
700runs · 7 frontier models
90.6%task success, verified onchain
94.8–99%frontier-cluster success rate
9safety pauses correctly taken
Read the research

INTERACTIVE SETUP

Connect the surface you chose.

npx skills add aomi-labs/skills
SESSION · Claude Code · Coding agent + local CLI
BuildSimulateAwaiting signatureDeterministic fixture · no live chat, wallet, or chain call
aomi-transactaomi-build

Install in your coding agentOne skills repository installs the Transact and Build instruction sets. Transact then calls the local Aomi CLI for account and signing operations.

  1. 01Installs aomi-transact
  2. 02Installs aomi-build
  3. 03Works with supported skill-aware coding agents

ONE TASK, FOUR PATHS

Same prompt. Different place to run, keep state, and sign.

They compose. MCP gives any client the catalog and the account thread; Skills give a coding agent the guided local workflow; the CLI is where a pending request gets simulated and signed.

SurfaceTalks toRuns whereStateSigning
Skillsaomi-transact · aomi-build
Agent API, through the CLIYour machineLocal session · ~/.aomi/Local key · tx sign
  1. agent reads SKILL.md
  2. aomi chat --new-session
  3. tx list
  4. tx simulate
  5. tx sign
MCP · agent/v1/agent/mcp
Agent API · aomi_chatAomi serverThread on your accountHand-off → portal or CLI
  1. aomi_chat
  2. aomi_check …
  3. awaiting_user
  4. sign in portal / CLI
  5. aomi_check ✓
MCP · pipeline/v1/pipeline/mcp
Pipeline API · catalog + toolsAomi serverStateless · App passed per callHand-off → portal or CLI
  1. aomi_list_apps
  2. aomi_select_app
  3. aomi_list_tools
  4. aomi_describe_tool
  5. aomi_call_tool
CLI@aomi-labs/client
Both · chat and txYour machineLocal sessions · session resumeLocal key · tx sign
  1. aomi chat
  2. tx list
  3. tx simulate
  4. tx sign
  5. session resume
Read the execution handoff guide

USE THEM TOGETHER

One execution workflow can continue across every surface.

Prompt

“Find my USDC balance on Base, then prepare a simulated deposit.”

01

Skills teach the workflow

Give the outer agent durable instructions for choosing chain context, simulating first, and stopping at approval.

02

MCP creates the hosted thread

The client works inside an OAuth-authorized, account-owned Aomi conversation without receiving wallet secrets.

03

Portal makes review visible

Open an awaiting request in a visual wallet surface to inspect the exact staged action before approval.

04

CLI resumes and signs

Pick up the same supported session locally, simulate again, and sign from the machine that controls the wallet.

READY WHEN YOU ARE

Start where your agent already works.

Install Agent Skills Connect MCP Install the CLI