Long context needs bounded admission
The exported GLM 5.3 record advertises 1M context, 128K output, and a defined reasoning list.
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 exported GLM 5.3 record advertises 1M context, 128K output, and a defined reasoning list.
What this means for Noemad
The service profile may impose smaller limits. Admission must enforce its own byte and token boundaries before requesting payment; raw catalog maximums are not the product contract.
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