Skip to content
CampaignsDesign reference · Preview

Scheduled access windows

The archived topic used a recurring time window for an eligible model.

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 archived topic used a recurring time window for an eligible model.

What this means for Noemad

Show the timezone, next boundary, applicable profile, and cap. An unknown clock or missing campaign configuration must not be interpreted as an active discount.

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
PREVIOUSShared campaign capacityNEXTPublish terms with a rate change