TameionSep 27 – Oct 10, 2026

Your agent decides.
Aomi makes the action executable.

A financial agent can decide. Aomi turns that decision into a transaction you can simulate, check, and hand to a signer. Start with one action you can inspect.

Where Aomi fits

One action. Your rule. Their signature. A receipt.

Circle and Arc already give you the wallet, the USDC, and settlement. You write the business rule. Aomi turns the agent’s decision into a transaction you can simulate, check, and hand to the signer.

01

The agent proposes

One payment, one reserve move, or one refusal. A decision is not a transaction.

02

Aomi constructs it

The exact call, chain, recipient, and amount, then a simulation of that payload.

03

Your rule decides

Invoice, vendor, milestone, budget, or risk. A prompt cannot talk past a check you wrote in code.

04

The wallet signs

The signer keeps the keys. Aomi does not give the agent authority to sign.

05

Arc settles

Commit Service follows the action to a confirmed result. A hash is not settlement.

06

You keep the receipt

Chain, status, sender, recipient, and value, checked on an explorer you do not control.

Circle and Arc

Wallets, USDC and EURC, payment rails, and settlement.

You

Who may be paid, how much, and whether this action already happened.

Aomi

Construction, simulation, the policy check, and the path to a signer.

Read the transaction pipeline

The problem

A valid payment can still pay the wrong person.

A ledger can balance while a vendor address is wrong, an invoice is duplicated or a retry pays twice. Builders need checks tied to the intended action, and evidence of what actually happened onchain.

From Canteen’s Agents and Ledgers research
01

Wrong recipient

Compare the proposed address with an approved payee before signing.

02

Wrong action

Check the exact call, amount and result against the business rule.

03

Unclear outcome

Treat the receipt as evidence. A returned hash is not settlement.

What Aomi supports on Arc

2 networksArc mainnet (5042) and testnet (5042002), supported today
6 toolsStableFX, from quote to settlement status
0 keys heldNon-custodial. Your signer keeps authority.

Why Aomi

Don’t rebuild the execution layer.

Aomi is the execution harness for onchain finance: the layer between an agent’s decision and the signature that makes it real.

Read the full developer reference
01

Non-custodial, always

Users keep their keys. The agent can propose an action. It cannot sign one.

02

Simulate before sign

The action is rehearsed on a fork of live state before anyone is asked to approve.

03

Policy in code, not in the prompt

Chains, contracts, recipients and amounts are limited in code. The agent cannot talk its way past a guard.

04

One integration, many venues

Arc sits next to Ethereum, Base, Solana and the other networks Aomi already runs. You build against one interface.

05

Hosted runtime, no infra

You write the tools and the prompt. Aomi runs the loop. Account abstraction is not available on Arc.

06

Every surface from one deployment

The same App can run in the Portal, a widget, the CLI, Skills, MCP, the API and Telegram.

Five requests for builders

Pick one money problem. Finish the flow.

Tameion’s five requests are prompts, not tracks. A project has to run on Arc, with USDC actually moving, for a business that is using it. Your own company counts. A synthetic dataset does not.

01

Intelligent Business Treasury

How does a business keep cash available while deciding what to allocate or reserve?

You decide which cash to reserve. Aomi constructs and simulates that one movement. Start from circlefin/arc-fintech, including USYC. A USDC and EURC trade is the StableFX path, and it needs a Circle credential.

Treasury · USYC · reserve moveForecast one cash need, then move one idle balance only when that rule says so.circlefin/arc-fintechStableFX path
02

AP/AR Automation Agent

Can an agent read invoices and pay the right vendor only once?

You verify the invoice, the payee, and that this invoice was not already paid. Aomi constructs the USDC transfer and stops for review.

USDC payment · recipient check · receiptReject a duplicate invoice or a changed vendor address.Worked payment
03

Contractor & Vendor Network Manager

How should verified work turn into an authorized milestone payment?

You own reputation, discovery, and the milestone check. Aomi covers the reviewed transfer after that check. Start from circlefin/arc-escrow.

Escrow · milestone · reviewed paymentRelease one payment after a verified milestone.circlefin/arc-escrowReviewed payment
04

Autonomous Business Operator

Which obligations can an agent pay without losing sight of the company’s cash?

You set the budget rule. Start from circlefin/arc-x402-circle-wallets when the agent pays an x402 service from its own Circle wallet. A transfer you review in the Aomi Portal is a different payment. Aomi runs the bounded execution after your rule.

Budget · x402 or reviewed paymentRun one workflow from money in, to one allowed payment, to a log.circlefin/arc-x402-circle-walletsReviewed payment
05

Compliance Intelligence Agent

How can changing counterparty risk affect a payment before it is sent?

You write the screening rule that allows, refuses, or escalates. Aomi prepares the action and stops it when that rule refuses. Simulation is not a compliance decision.

Policy input · guarded action · evidenceBlock one previously approved recipient after its risk status changes.Guarded execution

Source: Tameion’s official requests for builders

Recipes

A first action, then a real application.

One guided payment flow you can try in the Portal. Two more directions for teams with their own product or integration access.

Go first

Start small enough to verify.

One reviewed action, one deliberate refusal, and one confirmed result tell a stronger story than a dashboard full of untested promises.

Follow the quickstart

Tameion

Test USDC counts. Mainnet counts more.

Hosted by Canteen · invite-only · $40k in prizes · building on Arc

$32.5k is ranked: $10k for first, $7.5k for second, and $5k for each of three third-place teams. $7.5k is split across 10–12 standout teams, about $650–$750 each.

Submit by October 10, 11:59 PM ET. You need a public GitHub repo and a recorded demo under 3 minutes. A live URL is encouraged. You can submit more than once. There is no demo day. Judges review the form, the repo, and the video.

They will ask how many businesses you have onboarded, how much value the agent moved, and what problem you are solving. Your own company counts. A synthetic dataset does not.

30%

Agentic sophistication

How much the agent decides, and whether it can explain why.

30%

Traction

Real use during the event. Test USDC counts. Mainnet USDC counts more.

20%

Circle tool usage

Wallets, Paymaster, App Kit, CCTP, Gateway, USYC, contracts, USDC and EURC.

20%

Innovation

A new approach beats a polished repeat of a sample.

Examples

Projects on Aomi

Each project keeps its own rules and uses Aomi for the loop, the simulation, or the signature. Use them as references, then build your own.

Somm Finance

Actively managed DeFi strategies. Agentic Somm wraps Somm's five existing endpoints as typed tools, gives the agent its investment mandate in the system prompt, and renders the recommendation as a product-native card. Somm keeps its strategy, data and risk model. The same App serves the product frontend and Telegram. Aomi does not host a Discord bot.

Kuroko

An AI hybrid trading platform for prediction markets. Live Polymarket context in every message, market scoring, paper, testnet and live flows, stop-loss and take-profit guards. Uses the widget as its interface and @aomi-labs/client for trade intents. Unverified markets stay in simulation mode.

aomi-trader

A Hyperliquid trader that watches BTC-PERP, reads position and equity, and produces a LONG, SHORT, CLOSE or PASS decision each cycle. One session with @aomi-labs/client; the product owns risk threshold, size and cooldown. Proof that an Aomi product does not have to look like chat.

World Markets

In development. A Telegram asset manager on MegaETH that separates a product-specific mandate from the general pipeline: the App owns World Markets context and policy checks, Aomi supplies the loop, the channel, simulation and signing.

Aomi runs a simulate-first, non-custodial execution path on Arc mainnet (5042) and testnet (5042002), with a Commit Service that confirms settlement rather than trusting a transaction hash.