Model families are not interchangeable
The archive includes distinct Opus and Sonnet records, limits, rates, and supported reasoning levels.
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 archive includes distinct Opus and Sonnet records, limits, rates, and supported reasoning levels.
What this means for Noemad
Switching the backing model can alter cost and behavior. Treat a model change as an explicit configuration version, with representative output and tool-history checks.
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