Mandate as configuration
Value caps, allow-listed venues, risk bands, per-wallet rules — defined once, enforced on every action. Human-sync approval or autonomous execution within caps.
value capsallowlistsrisk bands
A manager already owns the hard part — the strategy. aomi runs everything between a decision and its settlement. Your existing logic becomes an agent that executes on every venue and chain, rehearses each transaction on a live copy of the chain before signature, and operates inside a mandate that is enforced, not promised. Keys stay with you the whole time.
Unedited screen captures of the execution layer a mandate would run on: cross-chain moves with a gas reserve, position rotations staged after simulation, and a multi-step sequence persisted to run on a cadence — so the mandate keeps executing after the desk closes.
An active manager already owns the difficult part — the models, the data, the risk framework, the endpoints a desk operates every day. What consumes the desk is everything between a decision and its settlement.
Each protocol requires custom code, dashboards, and monitoring — rebuilt per venue, per chain, and maintained through every upgrade and hardfork.
Markets run 24/7; operations teams do not. Rebalances, approvals, and liquidation guards depend on someone being awake — and headcount is the entire margin.
Post-Stream, depositors and allocators require proof that a vault does only what its policy permits — opaque discretionary execution is now a liability.
"Managing a single vault across multiple platforms means rebuilding everything from scratch — much like opening separate bank accounts with no shared infrastructure."
Manage idle treasury assets for Somm. Seek best net yield. Never exceed risk band B. Always propose before execution.
The architecture, the pipeline it enforces, the controls and posture around it, and the terms. Nothing here is bolted on — each is a property of the runtime, built directly on a full node that forks every chain in ~200ms.
The agent composes the exact transaction from strategy logic or an intent — batched into a single operation.
intent → exact txExecuted against forked, live chain state to prove the real outcome — slippage, balances, risk — before signature.
forked state · ~200msSigned by the mandate holder's own wallet under scoped delegation — human-approved or autonomous within caps.
AA bundler · signer's walletConfirmed onchain with account abstraction and Solana Jito built in — no separate infrastructure to run.
AA + Solana JitoValue caps, allow-listed venues, risk bands, per-wallet rules — defined once, enforced on every action. Human-sync approval or autonomous execution within caps.
Delegation is data, not a handover: halt an agent instantly, revoke a grant instantly. A failed simulation or an out-of-policy proposal stops before signature — by construction.
Non-custodial by construction. Agents sign through provider-native scoped delegation — Privy & Para compatible — and signing authority never transfers. The runtime's counter reads KEYS HELD: 0, always.
Per-app telemetry on every turn; each action traceable to its originating intent. An audit trail consumable by fund administration, auditors, and allocator due diligence.
The invariant: aomi can compose and simulate any transaction, but can only ever propose it. Authority to move value remains with the mandate holder's wallet and policy — including for strategies that run unattended.
Pricing follows the market's own convention — basis points on executed flow, not seat licenses. Rates are transparent and visible per application; the same rails allow an application to price and settle a fee of its own, as Somm does. Costs scale with results, and the platform earns only when flow actually settles.
Existing strategy logic, existing keys, an enforced policy — running as an agent that executes, reports, and settles fees on every chain.
Request the due-diligence pack →