The provider reference
Spend limits differ by provider, product and account. This reference separates the existence of a control from the ability to read or change it through an API.
Initial scope under evaluation
API spending and enterprise seat products are separate administrative boundaries. A feature on one does not imply the same feature on another.
Provider-capped
Provider-capped
Provider-capped for covered member usage; no API-writable pooled organisation or group cap established
Provider-capped only as an expiring attestation; otherwise velocity-bounded if all material dimensions qualify, else unbounded
Beyond the initial scope
Organisation and user spending policies are recorded in the source research. API read and write capabilities remain an open question.
Open
Outside the first scope. Cloud budgets, quotas and model-service controls require separate verification; no provider-wide cap capability is asserted here.
Out of first scope
Evidence behind the reference
The review date above is preserved from the product research. Documentation can change. Use these primary sources to check current availability and the permissions required for your account.
New to the terminology? Read the guide to budgets, caps and rate limits.
Let’s start with your AI estate
Help shape SpendAssure around the spending controls, approvals and reporting your team actually needs.
Talk about early access For finance, FinOps and platform teams.
SpendAssure