A campaign should expire predictably
A second archived topic covered a 48-hour discount window. The historical date in this route is a reference identifier, not a Noemad release date.
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
A second archived topic covered a 48-hour discount window. The historical date in this route is a reference identifier, not a Noemad release date.
What this means for Noemad
Use explicit UTC boundaries and immutable quotes. At expiry, new requests use the current terms while accepted quotes retain the rules they were issued under.
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