Entitlements belong to the account
The account reference distinguishes shared account limits from tighter per-key scopes, budgets, concurrency, and expiry.
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 account reference distinguishes shared account limits from tighter per-key scopes, budgets, concurrency, and expiry.
What this means for Noemad
Noemad’s MVP uses a wallet identity and per-run payments. Future rewards and campaigns need per-request eligibility rules and must not silently change already-approved terms or create a top-up 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