OpenAI

What each plan can show

OpenAI publishes a bill for the API and per-person analytics for ChatGPT Enterprise and Edu. Codex reports its own usage to LevelFour on any plan, and so do your own apps through OpenTelemetry. Chat in ChatGPT is measured on Enterprise and Edu alone: on Business, Plus and Pro, OpenAI publishes nothing about it, and it does not run on your machine.

Connect any mix, in any order. Billing data holds no activity, so add Codex usage beside a bill to see sessions, prompts and tools next to what you pay.

A source can hold more than one account: a second OpenAI organization, a second ChatGPT workspace, or a settings block per team. Add another at any time from the same page. Name is optional free text, and LevelFour uses it only to tell accounts apart.

A ChatGPT workspace billed in credits shows credits. LevelFour does not turn credits into dollars, because the price of a credit is set in your agreement.

History and what is left out

Prerequisites

Connect

Open Connect Providers and select OpenAI. The first time an admin opens it, Connect OpenAI starts by itself; after that, click Add account. Pick each plan your company pays for and click Continue:

Two plans with the same source share one step. You can skip a step or hand it to a colleague, and a review at the end lists what you connected and what is still open. Run it again at any time: it only adds accounts. Only admins connect, rotate and disconnect; a member or viewer sees each account and its status.

[otel]
log_user_prompt = false
exporter = { otlp-http = { endpoint = "https://api.levelfour.ai/api/v1/otlp/v1/logs", protocol = "json", headers = { "Authorization" = "Bearer l4i_..." } } }

pip install opentelemetry-distro opentelemetry-exporter-otlp-proto-http opentelemetry-instrumentation-genai-openai

OTEL_TRACES_EXPORTER=otlp
OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://api.levelfour.ai/api/v1/otlp/v1/traces
OTEL_EXPORTER_OTLP_TRACES_HEADERS=Authorization=Bearer%20l4i_...
OTEL_TRACES_SAMPLER=always_on
OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=false

What LevelFour keeps from Codex

Codex reports each thing a developer does as an event. LevelFour adds it to a daily total and stores the total, never one row per event.

LevelFour keeps usage, sessions, prompt counts and failed requests per person. Every other total covers all developers together and carries no name. Each person has one profile: the Codex version and terminal they last reported, and the first and last day they reported.

Codex reports no cost, so LevelFour values its tokens at OpenAI's API list price.

What LevelFour never reads

Codex sends a tool's arguments and output with every tool result. LevelFour discards them unread. It never reads or stores:

• the text of a prompt or a response
• a tool's arguments or output
• a command
• file content

The settings block keeps log_user_prompt off, so Codex sends no prompt text.

Who a request belongs to

A developer signed in to Codex with ChatGPT shows under their email, in the CLI and in the ChatGPT app. Codex signed in with an API key names no person, so LevelFour shows the account, or the machine when there is none. A developer who runs the CLI on an API key can name themselves by setting OTEL_RESOURCE_ATTRIBUTES=levelfour.person=<their email> in the shell Codex runs in. The ChatGPT app does not read your shell's variables, which it does not need: it is always signed in with ChatGPT.

Sending through an OpenTelemetry Collector

You can put an OpenTelemetry Collector between Codex or your apps and LevelFour. Have it export OTLP over HTTP, as JSON or protobuf, to the route of each signal: /api/v1/otlp/v1/logs for Codex and /api/v1/otlp/v1/traces for apps. LevelFour refuses gRPC, a batch over 2 MB, and a batch that holds more than 1,024 model calls.

exporters:
  otlphttp/levelfour:
    traces_endpoint: https://api.levelfour.ai/api/v1/otlp/v1/traces
    headers:
      Authorization: Bearer l4i_...
processors:
  filter/genai:
    error_mode: ignore
    traces:
      span:
        - >-
          attributes["gen_ai.usage.input_tokens"] == nil and attributes["gen_ai.usage.prompt_tokens"] == nil
          and attributes["gen_ai.usage.output_tokens"] == nil and attributes["gen_ai.usage.completion_tokens"] == nil
service:
  pipelines:
    traces/levelfour:
      receivers: [otlp]
      processors: [filter/genai]
      exporters: [otlphttp/levelfour]

The filter keeps only the spans that carry token counts, so the rest of your traces stay with your own backend. It reads the counts rather than gen_ai.operation.name, which older instrumentations leave out. An app that calls both OpenAI and DeepSeek sends through a Collector with one exporter per vendor, each with its own key: LevelFour leaves out a call that a key of the other vendor sent.

What you see

OpenAI spend appears under Costs and Usage and on its own OpenAI board under Boards, which appears once you connect a source.

Billed and usage value

LevelFour keeps two figures apart, and a switch on the chart and the table chooses between them.

• Billed is what OpenAI charges you through the API, and what a ChatGPT workspace billed in dollars reports.
• Usage value is Codex and app usage priced at OpenAI's API list price. It estimates what that usage would cost per token. LevelFour never adds it to a billed total.

The OpenAI board

The board sorts its cards into groups under headings. A card appears once it has data, and a heading appears once its group has a card. Bill reads OpenAI Platform and ChatGPT Enterprise. Every other group reads what Codex and your apps report, with the current day included.

Cards that compare people need two or more people who reported usage.

Confirming it worked

Each account you connect moves to Connected on the OpenAI page. OpenAI Platform and ChatGPT Enterprise data appears in about an hour. Codex and app usage turn Connected after the first prompt or model call and Verify connection, and their figures appear on the board within minutes.

Rotating or removing access

Rotating a credential

Create a new key in OpenAI. On the OpenAI page under Connect Providers, click Rotate credential on the account, paste the new key, then revoke the old one where you created it.

You cannot rotate an ingest key. Disconnect the Codex or app usage source, keeping its data, generate the settings again, and replace the block or the variables wherever you put them.

Removing access

Click Disconnect on the account under Connect Providers, then revoke the key: an Admin key on the OpenAI Platform's Admin keys page, a workspace Admin key under Credentials > Admin keys in the ChatGPT Admin Console. Disconnecting a usage source stops its ingest key working at once. Remove the block or the variables so Codex or your app stops sending.

Troubleshooting

Next

• Connect Providers lists every provider you can connect
• Anthropic and DeepSeek connect the same way
• Virtual tags group your OpenAI spend by team, product, or any other dimension, alongside your other providers