Separate grants for separate models
The source offered separate promotional pools for two model families. This is an entitlement design scenario only.
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 source offered separate promotional pools for two model families. This is an entitlement design scenario only.
What this means for Noemad
Map the source concept to independently scoped per-request discounts or compensation. Explain eligibility and how a failed, partial, or uncertain operation affects the benefit; do not create a prepaid balance.
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