SpendAssureby e.LensSpend 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.
API spending and enterprise seat products are separate administrative boundaries. A feature on one does not imply the same feature on another.
| Product | Spend control | Write by API | Read by API | Control classification |
|---|---|---|---|---|
| OpenAI API | Organisation and project caps, monthly only; 429 on reach; slight overshoot possible | Yes, Admin API | Yes | Provider-capped |
| ChatGPT Enterprise | Workspace budget or overage limit; user, group and workspace limits | Yes, Spend Controls API | Yes | Provider-capped |
| Claude Enterprise | Monthly per-member limits inherited from organisation, seat-tier or group defaults, or overridden per user | Per-user overrides only; defaults are configured in claude.ai settings | Effective member limits, inheritance and period spend | Provider-capped for covered member usage; no API-writable pooled organisation or group cap established |
| Anthropic API (Console) | Workspace spend limit exists | No, Console only | No | Provider-capped only as an expiring attestation; otherwise velocity-bounded if all material dimensions qualify, else unbounded |
Documentation-level capability inventory. Entitlements, permissions and read or write behaviour vary by account and need checking on each one. No reviewed source establishes a numerical end-to-end overshoot bound; any measurement describes an observation, not a guarantee.
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
These products appear in the source research but were not verified to the same level. Open questions stay open.
Organisation and user spending policies are recorded in the source research. Whether they can be read or changed through an API is an open question.
Open question
Cloud budgets, quotas and model-service controls need separate verification; no provider-wide cap is asserted here.
Not covered by this review
We aim to review provider documentation monthly and when a reported change affects a control. Send corrections to hello@spendassure.com with the product, the source link and the claim concerned. Use these sources to check current availability and the permissions your account needs.
We walk you through the workspace on sample data and discuss what a pilot with your own invoices, exports and contracts would look like.
