Skip to content

ChatGPT Enterprise gets per-user AI credit controls for Codex spend

Original: New usage analytics and updated spend controls for enterprises View original →

Read in other languages: 한국어日本語
AI Jun 21, 2026 By Insights AI 2 min read 1 views Source

Enterprise AI budgets are moving from seat counts to actual credit consumption, and OpenAI is giving admins a sharper instrument for that shift. On June 18, 2026, OpenAI released new usage analytics and spend controls for ChatGPT Enterprise; its RSS feed lists the item at 17:00 UTC, after the freshness cutoff for this curation run.

The practical change is that ChatGPT and Codex credit usage now show up in the Global Admin Console in one place. Admins can track usage and credit trends over time, identify top users, break spend down across users, products, and models, and export the same credit data through a unified Cost API. That turns AI usage from a vague adoption story into data that finance, platform, and enablement teams can analyze together.

The timing matters because Codex is increasingly part of day-to-day enterprise workflows, not only an experiment for engineers. OpenAI included a customer example from Zipline, where engineering had been using Codex heavily and broader company adoption created a need for analytics and predictable limits. The broader signal is that companies want to scale AI use without discovering runaway consumption only after invoices arrive.

The new controls also change how capacity can be granted. Workspace owners can set a default limit for the whole ChatGPT Enterprise workspace, define limits for specific groups, and create individual overrides for people who need more room. End users can see credit usage against their available budget and request more credits with context about the work they are trying to complete.

This is not a model launch, but it is an infrastructure-level product change for enterprise AI deployment. As model access, agent workflows, and coding assistants consume credits at different rates, cost governance becomes part of the deployment architecture. The next thing to watch is whether customers use these APIs to build internal chargeback, budget alerts, and model-routing policies around ChatGPT and Codex usage.

Share: Long

Related Articles