<app>.pricing.toml beside your App manifest to define what your App
charges. Replace <app> with the App name used by your manifest.
If the file is missing, every App tool remains free. If the file is malformed
or invalid, Aomi refuses to load the App.
Complete example
get_idle_assets costs $1.00 and propose_trade costs
$2.50 after a successful call. The outcome rule charges 0.30% of a supported
transaction flow.
Top-level fields
Beneficiaries
Each[[beneficiaries]] block defines one payment recipient.
A rule that references a missing beneficiary is invalid.
Resource pricing
Add one[resources.<tool>] table for each priced tool.
The resource key must exactly match a tool name declared by the App. Aomi
binds the price to that App and tool. A pricing file cannot change the price of
another App’s tool.
The current schema supports flat prices only. One credit equals
$0.01.
Aomi charges the price only when the tool returns successfully.
Outcome pricing
Add an[[outcome]] block to charge a percentage of a supported transaction
flow.
One basis point is 0.01%. A value of
30 charges 0.30%. Aomi calculates the
fee from the asset amount in base units and drops values that round down to
zero.
Outcome fees apply only when the transaction exposes a supported input flow.
Aomi adds the fee to the same smart-account transaction as the requested
action.
Validation errors
Aomi refuses to load the App when the pricing file contains any of these problems:- An unsupported
version - Malformed TOML or an unknown field inside
pricing - A negative, infinite, or non-numeric flat price
- A resource key that does not match an App tool
- A missing beneficiary reference
- An unsupported beneficiary type or invalid EVM address
- An outcome fee outside the valid basis-point range
Related pages
Fees
Understand the complete App fee model.
x402 payments
Learn how Aomi collects tool fees in USDC.