Quote, authorize, reconcile
A bounded request requires an immutable rate snapshot, a maximum authorization, and separate actual-cost settlement.
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 bounded request requires an immutable rate snapshot, a maximum authorization, and separate actual-cost settlement.
What this means for Noemad
Qualification must cover the worst permitted request. Preserve the original authorization through reconciliation. Settle measured actual usage once; unused maximum stays in the wallet, and missing usage is not charged as the cap.
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