The OpenAI usage dashboard is one bill. It is not cost per customer.
Fair: the platform usage view is the org bill, and it can group by key. Gap: your tenants and features live in your product.
OpenAI’s usage and costs views are the org bill. The APIs can group_by project, API key, and a user label. Spend limits exist at org or project. That is their dashboard. This page is not it.
Your customers and features are not OpenAI objects. CostSlice tags x-cs-tenant and x-cs-feature and shows a customer P&L. You keep the OpenAI API key.
| Job | OpenAI usage | CostSlice |
|---|---|---|
| Project / key / user label | Yes | Not a replacement for the org bill |
| Your customer / feature | No | Customer P&L |
Playbook: track OpenAI cost by customer. Allocate by tenant. Demo: sample P&L.
Worked example: OpenAI’s usage view would add acme-health into the org total. The sample splits that customer at $4,812 / $2,400 / −101% from the healthy rows. That split is the job.
Starter is free. No credit card. Operator: Media Yard LLC, PO Box 73, Pennsauken, NJ 08110. hello@costslice.com
Questions
- Does the OpenAI usage dashboard show cost per customer?
- No. It is the org bill. It can group by project, API key, and a user label. It does not know your tenants.
- Can the Costs API group by my tenant id?
- No. group_by is project, API key, and user. Your customer id lives in your product.
- Is CostSlice a replacement for the org bill?
- No. Keep the OpenAI usage view for the company total. CostSlice is the customer P&L next to it.
- Do you store prompts?
- No. We store counts and tags. Not bodies.