Skip to main content
Telara

Integrations / OpenAI Codex

OpenAI Codex logo

OpenAI Codex

OpenAI Codex (agentic coding) — Codex Analytics API for per-user credits/tokens and Compliance API for audit logs. Spend-only connector for the AI Platform Spend Governance feature.

API key
Spend
AI estate

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI YesRuns actions NoReal-time events No

Before you connect

Prerequisites

This connector requires a ChatGPT Enterprise workspace credential issued from the ChatGPT Enterprise admin panel. A standard OpenAI Platform key (sk-proj-... or sk-...) cannot access Enterprise compliance logs. For direct OpenAI API usage tracking, use the OpenAI Direct connector instead.
An OpenAI Enterprise workspace with Codex. ChatGPT Team and Plus do not expose Codex governance APIs.
Enterprise owner or admin who can issue an API key for Codex analytics.

Vendor setup

Get the credential

1
Open the Enterprise admin
Sign in at ChatGPT Enterprise. Open the admin workspace → API keys / Codex governance (Settings → Organization → API, matching current OpenAI admin wording).
2
Create an Enterprise key
Issue an API key for Codex governance. Copy the key and the workspace id from the same admin page. This is not a consumer sk-proj project key.
3
Paste in Telara
Settings → Integrations → OpenAI Codex. Paste the key and workspace id. ChatGPT Enterprise spend is a separate connector.

In Telara

Connect in Telara

API key

OpenAI Enterprise API key for Codex governance surfaces. Current Codex governance docs define a dedicated Analytics API for per-user credits/tokens and a Compliance API for audit records. The legacy stateful Compliance route was removed on 2026-06-05; use the unified Compliance Platform only for audit detail, not as the primary spend source. Verified docs: https://developers.openai.com/codex/enterprise/governance

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key
  • Workspace Id

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

Vendor history: 30 days of vendor-side history.

  • codex_tasks_started
    count
  • codex_tasks_completed
    count
  • codex_task_duration_ms
    ms
  • codex_tool_invocations
    count
  • codex_api_requests
    count
  • codex_sandbox_decisions
    count
  • codex_approval_prompts
    count
  • codex_threads
    count
  • codex_turns
    count
  • codex_credits
    count — Codex credits drawn from the workspace plan — the billable usage unit.
  • input_tokens
    tokens
  • output_tokens
    tokens

AI estate

What gets discovered

Config paths
  • ~/.codex/config.toml
Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths
  • .codex/config.toml
Resource kinds

mcp_client_configuration, mcp_server_deployment

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

This connector requires a ChatGPT Enterprise workspace credential issued from the ChatGPT Enterprise admin panel. A standard OpenAI Platform key (sk-proj-... or sk-...) cannot access Enterprise compliance logs. For direct OpenAI API usage tracking, use the OpenAI Direct connector instead.

Honesty

Known limitations

A project API key from platform.openai.com cannot read Codex workspace analytics.
Codex and ChatGPT Enterprise are separate Connect buttons on purpose so budgets can differ.