OpenAI
Arrakis covers two OpenAI products with a single tenant Admin API key: Codex (CLI + Desktop) and ChatGPT Desktop. The org-side surface is shared — one Admin API key reads workspace metadata, users, and Compliance Logs Platform events for both products. The endpoint-side story differs.
Primary data planes
- Codex — native OpenTelemetry (v0.143.0+) or MDM-shipped wrapper. Recent Codex CLI releases emit OTLP directly (service tier, reasoning effort, MCP tool call metrics). For older versions Arrakis ships a wrapper on PATH that exports OTLP env into an OTel-aware sidecar. → OpenAI Codex
- ChatGPT Desktop — org-side only. No documented OTel exporter, managed-settings file, or MDM policy schema. The only endpoint lever is network egress (workspace-forcing proxy). Coverage comes from the Compliance Logs Platform. → ChatGPT Desktop
Naming note (2025-12-11)
The Compliance API was renamed Compliance Logs Platform on 2025-12-11 and gained event/transactional endpoints alongside the pre-existing state-based endpoints. Both product pages use the new name; older OpenAI docs may still refer to the Compliance API.
Where telemetry lands
All coding-telemetry paths on this page terminate at the Arrakis coding-telemetry ingest, which runs the shared detection rules (typosquatting, secret exposure, template injection, tool collision, and others). Whether telemetry arrives as native OTLP, a hook-emitted event, or an admin-API pull, it is normalized into the same event registry.
Pages in this section
- OpenAI Codex — Admin Console + Compliance Logs Platform enablement; native OTel and wrapper deployment.
- ChatGPT Desktop — org-side Admin + Compliance Logs Platform coverage; endpoint-side reality check.