Organization settings / OpenAI Compliance Logs
OpenAI Compliance Logs
Connect ChatGPT Conversations and OpenAI Compliance Logs with an Admin key to import conversations, usage, and spend.
The OpenAI Compliance Logs integration connects OpenAI’s Compliance Logs Platform to import Codex and ChatGPT usage and spend for the organization, feeding the platform’s Observability and Costs views. Codex cloud surfaces such as web tasks and GitHub code review emit no device telemetry, so this feed is their only token source. These imports are post-hoc logs: usage on log-only surfaces can be observed and billed, but not blocked in real time.
OpenAI also has a separate ChatGPT Conversations import that reuses the same API key but a different identifier: a ChatGPT workspace UUID rather than an organization ID. It imports conversation content instead of cost: ChatGPT conversations and Codex cloud web-task transcripts, both surfaced as agent sessions. Follow the ChatGPT Conversations setup steps below to connect it. If both are connected, don’t confuse the two ID fields when configuring them.
Access requirements
Section titled “Access requirements”Viewing connection status on the AI Integrations page requires the org:read scope. Connecting, configuring, or deleting the integration requires the org:admin scope, held by the default Admin role.
Create the credential
Section titled “Create the credential”Create an Admin key in the OpenAI admin console, not a regular API/secret key or access token from the platform console. Both ChatGPT Conversations and OpenAI Compliance Logs use this key with the same read-only permissions:
- Open admin.openai.com and select the organization you want to connect.
- Scroll down to Developer access in the navigation and select Credentials.
- Open the Admin keys tab and click Create new admin key.
- Set permissions to Custom.
- Set Compliance Logging Platform to Read. Leave all other permissions disabled; this integration does not need them.
- Create the key and copy its value for the Speakeasy configuration below.
Choose the identifier for the integration you want to connect: a ChatGPT workspace UUID for conversations, or an OpenAI organization ID starting with org- for usage and spend.
Connect ChatGPT Conversations
Section titled “Connect ChatGPT Conversations”Open Organization settings > Settings > AI Integrations, find ChatGPT Conversations, and click Configure. Enter:
- API key: the Admin key created above. If you’ve already connected OpenAI Compliance Logs, you can reuse that key.
- Workspace UUID: the UUID of the ChatGPT workspace you want to import. Use the workspace UUID, not the OpenAI organization ID starting with
org-.
This integration imports ChatGPT conversations and Codex cloud web-task transcripts into Agent sessions. You don’t need to connect OpenAI Compliance Logs to import conversations; that separate integration imports usage and spend.
Connect OpenAI Compliance Logs
Section titled “Connect OpenAI Compliance Logs”Open Organization settings > Settings > AI Integrations, find the OpenAI Compliance Logs provider, and click Configure. Enter:
- OpenAI Compliance Logs API key: the key from above.
- OpenAI organization ID: must start with
org-; the dashboard rejects values in any other format when you save.
Verify the Compliance Logs connection
Section titled “Verify the Compliance Logs connection”The integration doesn’t test the credential synchronously on save; the first scheduled poll does. The Codex & ChatGPT cost metrics stream polls roughly every 5 minutes, with an initial 30-day lookback on first connect. If the key is invalid, OpenAI rejects the request and the stream shows a rejected-credential status with a Retry now action once you’ve fixed the key. A stream that keeps failing auto-pauses after three consecutive rejections rather than retrying indefinitely against a bad credential.
Once polling succeeds, Codex and ChatGPT usage and cost data start flowing into Observability and Costs.