Keep cache usage visible
Some models report cached input separately from ordinary input; a missing cache field is unknown rather than zero.
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
Some models report cached input separately from ordinary input; a missing cache field is unknown rather than zero.
What this means for Noemad
Retain each reported usage field, apply the pinned model rate, and show the calculation in the receipt. Never infer a cache hit merely because a prompt looks familiar.
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