Make every billing unit explicit
The archived pricing design separates input, output, cache reads, minimum charges, and modality-specific units.
A topic from the capability archive
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
The archived pricing design separates input, output, cache reads, minimum charges, and modality-specific units.
What this means for Noemad
Model costs and customer USDC prices belong to separate ledgers. A quote must identify the profile, unit, limits, and version rather than relying on a page-wide conversion rate.
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