Qualifying a new model generation
The archived catalog contains a Claude Opus 5 reference with a 1M-token context, 128K output, and explicit reasoning levels.
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 catalog contains a Claude Opus 5 reference with a 1M-token context, 128K output, and explicit reasoning levels.
What this means for Noemad
A catalog record is a qualification candidate. Tests must verify the selected credential, supported tools, output limits, structured responses, and errors before any Noemad profile advertises it.
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