OpenAI moves Enterprise API cost details out of invoices
Reviewed by Helen Jones
OpenAI says that Enterprise API invoices issued from 1 April 2026 no longer carry detailed cost lines; the replacement is a cost-data export from the API Usage dashboard. The same dashboard can export monthly or month-to-date cost data, while activity data can be grouped by project, user, API key, model, batch, or service tier.
A monthly invoice is a receipt, not a diagnosis. If all of your product’s API calls sit in one project or use one undifferentiated key, you can see that spend rose but cannot tell which part of the product—or which experiment—created the change. The dashboard’s cost and activity exports give you a lighter first control than a full observability platform: separate revenue-critical features into projects or keys, then inspect the export before the monthly close. That will not calculate customer-level margin for you, but it makes the next cost investigation smaller and sooner.
Analysis
Before the next invoice, open the API Usage dashboard and export one month-to-date Cost CSV grouped by project. If everything still lands in one project, write down the two product features that need separate projects or keys before you add another agent step.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "OpenAI moves Enterprise API cost details out of invoices", Collab365 Spaces.