Your users want limit orders, stops, and DCA — order types your venue doesn't ship, and each one a fill you'd earn a fee on. aomi runs them for you, as background agents trading from the user's own wallet. Every trade is rehearsed on a live copy of the chain before it is signed, so it lands or it never leaves. One integration, every chain.
Unedited screen captures. Routing, bridging, position rotation and scheduled execution — each stated in one sentence, each proven against live chain state before a signature exists. The last one keeps running after the tab closes: that is the order type your venue doesn't ship.
Builder codes settled the question of whether a venue will pay a frontend it didn't build: it will, per order, automatically, and it already has — at scale. What the venues don't ship is everything that happens between orders.
| Frontend | Builder revenue | Users | Revenue / user |
|---|---|---|---|
| Phantom | $20,630,022 | 137,496 | $150 |
| Based | $15,056,894 | 42,579 | $354 |
| PVP.trade | $7,946,185 | 28,189 | $282 |
| MetaMask | $6,510,547 | 43,761 | $149 |
| Insilico | $3,306,853 | 2,962 | $1,116 |
The gap: perp venues give you spot and market orders. Limit, stop-loss, trailing, DCA, scheduled rebalancing and copy execution all have to run somewhere off the venue — continuously, per user, without holding their keys. That's the layer aomi is.
aomi runs its own full blockchain client, so it can spin up a private copy of any chain — a fork of live state — in ~200ms. Every trade goes through the same four steps: build it, rehearse it on that copy, have the user's own wallet sign it, broadcast it. Account abstraction and Solana Jito come built in.
Compose the exact transaction from an intent or a strategy — multi-step routes batched into a single operation.
intent → exact txExecute against a fresh fork of live chain state. Slippage, balances and the real output are known before anything is signed.
forked state · ~200msSigned by the end user's own wallet under scoped, revocable delegation. Your platform never takes custody.
AA bundler · user's walletConfirmed onchain with account abstraction and Solana Jito. No separate broadcast infrastructure to run.
AA + Solana JitoLimit, stop-loss, trailing stop, DCA, scheduled rebalancing and copy execution run server-side and keep working after the user closes the tab — each one a fill you charge a builder fee on.
The same execution layer serves your web frontend, Telegram, Discord and Slack from one runtime — no separate build per channel.
EVM and SVM behind one interface. Adding a chain is configuration, not a quarter of engineering and a new broadcast path.
Every tool call is priced and settled on-rails, so you can charge for what you ship — the same mechanism our launch partner Somm uses for app-level fees.
Reasoning costs time. Simulation costs time. Both are free at some horizons and disqualifying at others, so here is the line rather than a claim you'd have to benchmark to disprove.
Also worth saying plainly: copy execution has a structural ceiling no infrastructure removes — the lead's own price impact lands before the follower does. We'll help you ship it and cap the damage with simulation and slippage bounds; we won't claim to make followers match leaders.
Most execution automation in this market runs on stored exchange API keys or a hosted burner wallet. Both concentrate the blast radius on your servers — and the industry has the incident history to prove it.
"Export Private Keys: Shows your Private Key to export for external use."
Execution runs under a revocable, permission-limited grant from the user's own wallet — Privy and Para compatible. aomi holds zero keys, and the runtime's counter says so.
Value caps, allow-listed venues and per-wallet rules are checked outside the model. Published research shows prompt-based defenses fail against memory injection; ours isn't one.
Halt execution or revoke a grant immediately. A failed simulation or an out-of-policy order stops before signature, by construction.
One runtime serves all your users. No container per user — the line item that otherwise scales linearly against you as you grow.
No seat licences, no demo gate, no annual minimum to start. Build against the sandbox today; pay when your users execute.
Simulation before every signature, keys that never leave the user's wallet, one runtime across every chain and surface — and a fee line on every fill it lands.