“Move most of my ETH over to Base, but leave enough on mainnet for gas.” Across handles the bridge and preserves a gas buffer.
“Now stake the rest with Marinade.” The swap settles, then a follow-up instruction in the same thread. Solana.
“Move my entire mSOL position over to JitoSOL.” Routed through Jupiter at ~0% price impact; simulation passed, staged for approval.
“Yes, do the whole sequence.” The Lido, Aave, and ERC-20 steps persist as a recurring intent.
Architecture overview
The pipeline on the left is the contract every chat-initiated action passes
through. The runtime on the right is what your team does not build:
stateless dispatch, per-user agent threads, tool and model scheduling, and a
fork of every chain served from a full node. Language in, verified execution
out.
How to use
Tell an agent what you want and it turns plain English into wallet-signed transactions. As a human, use the product directly at chat.aomi.dev: connect your wallet and start chatting to trade. Coding agents such as Claude, Codex, and Hermes can use Aomi through the MCP server. For headless access, run theaomi CLI from
your terminal.
Try the portal
Connect a wallet at chat.aomi.dev and trade by chat. No install.
Agents with MCP
Point Claude Code, Cursor, or any MCP client at the Aomi server and trade
from your editor.
Access through the CLI
Install
aomi, chat, simulate, and sign from the terminal.Integrate with the SDK
Call Agent or Pipeline from TypeScript, raw HTTP, React, or the widget.
How to build
You can build Aomi Apps as plugins similar to ChatGPT plugins and Claude connectors, but for onchain execution. Wrap your API as a small set of tools, add a system prompt, and deploy it. The runtime loads your plugin, and your agent inherits simulation, non-custodial signing, and every supported channel.Overview
What an Aomi App is and the four steps from idea to live.
Quickstart
From an empty folder to a deployed App in about ten minutes.
Developer Platform
Create, deploy, and operate Apps from the browser at build.aomi.dev.