Noemad Docs
Approve a maximum. Pay for usage.
The x402 v2 upto flow separates authorization from actual settlement.
Review a model-specific quote
There is no user app balance to top up. Pricing comes from the selected model and parameters. The gateway freezes the rate snapshot, unit, modifiers, conversion policy, limits and expiry for the operation.
| Field | Meaning |
|---|---|
| Maximum | An enforceable upper bound you approve before dispatch |
| Actual amount | Calculated from reliable request usage and the frozen rate |
| Network | Monad; chain, token, proxy and facilitator must come from verified configuration |
| Mechanism | x402 v2 upto, using the pinned Permit2/proxy implementation |
| Network fee | Separate from inference; sponsorship must be verified |
| Current chat route | Live chat maximum: 0.01 testnet USDC. The actual amount remains pending until the supplier bill is resolved. |
The request lifecycle
- Validate the capability, capacity and model rate.
- Create an immutable quote and return a payment challenge.
- Review the quote and any required allowance.
- Sign the bounded request authorization in the wallet.
- Verify and claim one operation before dispatch.
- Forward output and record reliable usage.
- Persist the actual amount and unique settlement job.
- Verify the matching onchain receipt before marking collection settled.
The unused amount stays in your wallet
The maximum is not transferred first. Settling less than the maximum leaves the difference in your wallet; it is not a refund. Authorization also does not lock your balance, so later collection can fail.
Metering and rounding
Chat separates ordinary input, cache-read and output under the model’s usage definition. Media uses its actual units. Money uses integer/fixed-point values. Current policy converts 100,000,000 nominal Amanai credits to 1 USDC and rounds the final request charge up once to 0.000001 USDC. The platform fee is zero. The supplier bill already incorporates model and cache pricing; the gateway does not charge cache twice.
Uncertainty and zero charge
Missing usage is not permission to charge the maximum. Reconcile uncertain outcomes. A free or rounded-zero operation closes as zero-charge without inventing a transaction. Poll the existing operation; the gateway reconciles uncertain settlement and does not blindly send a second payment.
Implementation status
The backend has a recorded testnet wallet payment below its cap. The public dashboard uses the SDK checked against the Go verifier; acceptance of a new signed request through this deployed UI is tracked separately. Other models, mainnet and media payments are not enabled.
Protocol references: Monad x402 guide and EVM upto specification.