Reconcile model-family usage
Provider-specific usage formats can expose input, output, cache reads, and cache creation through different fields.
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
Provider-specific usage formats can expose input, output, cache reads, and cache creation through different fields.
What this means for Noemad
An adapter must preserve useful distinctions and reject incomplete or inconsistent usage. Only publish a price after the exact model route and limits have been qualified.
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