The 15Five AI Codex integration connects your ChatGPT Enterprise workspace to 15Five AI, syncing per-user, per-day Codex adoption and usage signals so agents can surface how your engineers are using Codex and where it's driving impact. The integration connects through a single OpenAI API key that must be scoped to the Codex Analytics API by OpenAI Support — this scoping is not self-serve. Prompt content, generated code, and conversation contents are never read. This integration requires a ChatGPT Enterprise plan. Syncing is available now; insight features are coming soon.
Access and Availability
| Role | Requirement |
|---|---|
| OpenAI API Platform owner or admin | Required to create the API key and submit the OpenAI Support request to apply the Codex Analytics scope |
| 15Five Company Admin, HR Admin, or IT Admin | Required to connect the integration from Agents Hub |
Note: To ensure the highest level of security, 15Five is continually investing in our overall information security program, resources, and expertise. To review 15Five's security documents, and how we handle your company data, see our Trust Website.
Feature Structure
The integration is configured from Agents Hub > Integrations > Codex.
How Access Works
A few things to know about how 15Five AI works with your Codex data:
Usage signals only — never prompt or code content. The integration reads usage metadata from the Codex Analytics API: who used Codex, how much, and how they engaged with Codex's code reviews. Prompt content, generated code, file contents, and the contents of Codex conversations are not read.
One scoped key defines the boundary. When OpenAI Support adds the Codex Analytics scope to the API key, that key becomes analytics-only — it can no longer be used for any other OpenAI API call. 15Five AI uses only that one key, and only for the documented analytics endpoints.
You set the scope in OpenAI. The key is your control point. You can revoke it from the OpenAI API Platform at any time, and 15Five AI's view stops at whatever the key can read.
Data Synced
Usage activity (per user, per day):
- Threads and turns — Codex sessions and interactions
- Credits consumed — Codex's measure of usage volume
- Token usage — text input, cached input, and output tokens
Code-review activity (per user, per day):
- Codex code reviews performed and comments generated, with priority breakdowns (P0, P1, P2)
- Engagement with Codex review comments — reactions and replies from your team
Never synced:
- Prompt or response content — Codex prompts, generated code, and conversation contents
- Source code — only counts and metrics are read, not the underlying code or diffs
- Full API key value — 15Five AI uses the key only against Codex Analytics endpoints and does not store the full secret beyond what's needed to make the request
Backfill and Sync Cadence
On first connect, up to one month of history is backfilled, typically completing within 24 hours. After that, records sync multiple times per day. There is no built-in data delay — the Codex Analytics API makes data available without the aggregation lag present in some other integrations.
Permissions
| Key | Scope | Purpose |
|---|---|---|
| Codex Analytics API key |
codex.enterprise.analytics.read (applied by OpenAI Support) |
Fetch per-user, per-day Codex usage and code-review activity |
Key Rules
- A ChatGPT Enterprise plan is required — the Codex Analytics API is not available on other plans.
- The Codex Analytics scope must be applied by OpenAI Support — it is not self-serve. OpenAI typically responds within 1–5 business days.
- The API key must be created in the OpenAI API Platform organization linked to your ChatGPT Enterprise workspace — keys from other organizations will not work.
- Once the Codex Analytics scope is applied, the key becomes analytics-only and cannot be used for any other OpenAI API call.
- The API key is displayed only once at creation — store it securely before closing the creation dialog.
- If the API key is deleted in OpenAI, it cannot be restored. A new key will require repeating the OpenAI Support request to reapply the scope.
- Syncing is available now; AI insights powered by Codex data are not yet live.
- The integration can be disconnected from Agents Hub > Integrations, or by deleting the API key in the OpenAI API Platform.