AOMI PLUGIN SDK

Bring your API. Ship an agent that can transact.

Package your proprietary product context and API operations as typed tools. Aomi hosts the application, manages its releases, and connects every selected tool call to the transaction pipeline shared across Aomi surfaces.

Developers build the polymarket-trader plugin, which reads their market API and hands the selected order to Aomi for construction, simulation, policy checks, and signer-controlled submission.

Build your first App Rust SDK reference

PLUGIN SDK APP

polymarket-trader

user-owned market API + Aomi transaction namespace
GET /markets/:idGET /orderbookHOST aomi.transactions
Product API stays yours.Market context enters through typed Plugin SDK tools; signing authority never does.
EXECUTION THREADBounded YES position
RUNNING
  1. USER INTENT

    Buy $500 of YES at 62¢ or better. Do not exceed my $500 market limit.

plugin APIAomi transaction pipelineuser-owned signerno live market, wallet, signer, or trade

ONE RUNTIME · TWO CAPABILITY LAYERS

Your API supplies the product. Aomi supplies the transaction path.

Each Aomi App is a Rust program composed of a role, typed tools, and a workflow. Aomi loads it in the hosted runtime, invokes the appropriate tool, and routes the resulting action into the transaction pipeline.

rust

Register the plugin role, tools, and Aomi transaction namespace.

1// The product-specific role and workflow.2const PREAMBLE: &str = r#"3Read the market, quote the requested outcome,4then pass the selected action to Aomi. Never sign.5"#;6 7dyn_aomi_app!(8    app        = client::PolymarketTrader,9    name       = "polymarket-trader",10    preamble   = PREAMBLE,11    tools      = [tool::ReadMarket, tool::QuoteOrder],12    namespaces = [transactions]13);

OPERATE · BUILD.AOMI.DEV

Institution-grade monitoring for transactions, tool calls, and fees.

Aomi Build keeps every release tied to its repository, compatibility status, runtime lifecycle, tool health, transaction outcomes, and operating cost.

Usage

Revenue, platform fees, and charges for your apps in this statement period. End-user spend is reported separately under Account → Billing.

Gross revenue$883.50collected from end users
Platform fees−$119.35revenue share
Service charges−$57.03model usage & hosting
Net+$707.12Jul 1 – Jul 15
Partner payments

Partner payments are liabilities owed to tool beneficiaries, not builder revenue. Settlements are reconciled at recipient-bucket scope because one receipt can clear fees from more than one app. Accrued and settled cover this statement; current outstanding is the live balance across all periods.

Statement · Jul 1 – Jul 15
Priced calls141 configured tool
Accrued$17.501,750 credits · statement period
Settled$15.001 receipt · statement period
Current outstanding$2.50all periods · recipient bucket
Configured prices
ToolPriceBeneficiaryObserved
rebalance_liquidity · sommelier-liquidity-manager125.00 credits · $1.25 / success0x5D90…4c9B · Base Sepolia14 calls
Payment activity
TimeEventAmountReceipt
7/27/2026, 10:37 AMSettlement confirmed · sommelier-liquidity-manager$15.00 · 1,500 credits0x55e5…df74 ↗
7/27/2026, 9:59 AMFee accrued · sommelier-liquidity-manager$2.50 · 250 credits—
RevenueJul 1 – Jul 15
SubjectAppEventsGrossPlatform feeNet
Tool invocationshyperliquid-arb-bot482$482.00$48.20$433.80
Outcome feespolymarket-trader31$155.00$46.50$108.50
Tool invocationsworld-market-telegram301$150.50$15.05$135.45
Tool invocationssommelier-liquidity-manager96$96.00$9.60$86.40
Charges
ItemAppEventsAmount
Model usagehyperliquid-arb-bot482$18.42
App hostinghyperliquid-arb-bot1$10.00
Model usagepolymarket-trader214$8.61
App hostingworld-market-telegram1$10.00
App hostingsommelier-liquidity-manager1$10.00
Model usage detailby provider/model

anthropic/claude-sonnet-4-631.8240

openai/gpt-5.2-mini12.4060

Token-level usage explains the base cost. Apps using customer-provided keys (BYOK) incur no model charges.
Open Aomi Build Read the docs

deterministic fixtures · no live account is contacted

BUILD → TEST → DEPLOY → OPERATE

Integration tooling and deployment pipeline.

The same toolchain carries a plugin from a platform-compatible build through local model testing, hosted activation, and the operational evidence that follows.

01aomi-build

Build

Check the platform SDK, then scaffold or compile the plugin as a loadable cdylib.

aomi-build compile
02aomi-run

Test

Load the compiled plugin locally, talk to it through a real model, and inspect which typed tools it selects before shipping.

aomi-run plugins/libapp.dylib
03release

Deploy

Publish the connected source, let CI cut the release, and activate the verified artifact in Aomi's hosted runtime.

aomi-build deploy
04build.aomi.dev

Operate

Track deployment and compatibility status, activation, tool health, usage, logs, metrics, and channel integrations.

status · logs · metrics

THE MANAGED DESTINATION · BUILD.AOMI.DEV

Developer console just like Vercel

Build and deploy end at Aomi Build: the managed control plane that keeps the repository, release, hosted runtime, and operating evidence together for every App. It is where teams manage what is live, what ships next, and how each App performs.

Manage your Apps
  1. 01Connect the repository
  2. 02Manage every release
  3. 03Operate the live App
Aomi Build overview showing projects, live deployments, recent releases, and operational navigation
Aomi Build project home showing live status, environment readiness, chat access, and project management details