Review the payment before signing
A wallet can identify the requester and authorize a maximum for a metered inference operation.
This note explains the design being adapted. It does not announce a shipped Noemad API, a verified model deployment, or a currently available promotion.
The subject
A wallet can identify the requester and authorize a maximum for a metered inference operation.
What this means for Noemad
Noemad targets USDC settlement on Monad. Model rates, enforceable limits, maximum, network, token, merchant, and expiry are pinned before approval. Actual usage is collected afterward; inference and collection states remain separate.
Before this can go live
- Implement the contract behind the relevant frontend controls.
- Validate ownership, limits, failure recovery, and the exact provider configuration.
- Publish authoritative availability and customer terms before accepting any payment.
- Keep request, payment, usage, and result records linked to one logical operation.
What you can explore now
The interface includes the corresponding documentation and navigation. Local samples stay clearly marked, and no service availability or account balance is inferred from a static catalog.
Explore the related reference