Source boundary
OpenAI
Confirm source eligibility in your workspace before creating access.
- Financial source
- Organization cost reports with usage attribution when supplied
- Reviewed
- 2026-09-17
- Cost bases
- net, billed, credits
- Useful dimensions
- organization, project, line item, model, API key, operation, service tier
Known limits
- Usage does not independently prove billed cost.
- Direct and cloud-marketplace billing remain separate.
Prepare the connection
Eligibility
An OpenAI API organization and an organization Admin API key with cost-report access are required.
An organization Admin key is required because OpenAI workload identities cannot access the Costs API.
Authentication choices
- Organization Admin key — recommendedPruneFox stores the credential encrypted in the isolated credential broker and never returns it to the browser.
Connection details
| Field | Why it is needed | Example format |
|---|---|---|
| Organization ID | Organization that owns the reported cost. | org-… |
| Admin API key | Organization Admin API key used only for approved cost and usage reporting operations. | Write-only value |
Permission boundary
| Resource | Read or bounded staging permissions | Purpose |
|---|---|---|
| Selected OpenAI organization | organization costs read, organization usage read | Read organization reporting without model invocation, project mutation, key management, or user administration. |
Connection sequence
- Confirm the organization—not a project—is the intended billing scope.
- Create or select a dedicated Admin API key.
- Enter the organization ID and key.
- Validate organization identity, cost access, usage capability coverage, daily bucket support, and pagination.
Validation and first sync
Validation rejects project-only keys, another organization, missing cost access, malformed cursors, or unsupported endpoints.
Daily organization cost buckets are paginated and reconciled first; usage families are fetched independently and cannot invent or replace billed cost.
Freshness: The Costs API is daily; usage context can arrive on a different cadence and remains separately labelled.
Remove access
Revoke the PruneFox connection, then revoke the dedicated Admin API key.
Troubleshooting
Check organization identity, Admin API access, daily time boundaries, pagination, and the distinction between cost and usage coverage.
Verify the first completed period
Compare one bounded completed period with the provider billing source. Match currency and cost basis, inspect credits and adjustments, and confirm that missing dimensions remain unavailable rather than zero.
Troubleshoot safely
Use the visible connection state, provider name, affected date range, and expected outcome. Never send credentials, raw billing exports, payment data, or customer records through support.