Connect OpenAI

Add your OpenAI Platform, OpenAI Analytics, and Compliance API keys so Tokenize can read API spend, Codex usage, and budgets.

Tokenize connects to OpenAI with up to three keys. Each comes from a different admin console and unlocks different parts of the dashboard. You can add any of them on their own.

The keys live in the OpenAI section of Settings → Providers. Click a section title, such as OpenAI Analytics, to open it. A check mark before the title means a working key is saved. The OpenAI Analytics and Compliance API key sections carry an Enterprise badge: they need a ChatGPT Enterprise workspace.

Who can do this: Admins in Tokenize. Each key also needs the right admin role on the OpenAI side, listed below.

Which key do you need

KeyWhere it comes fromWhat it unlocks in Tokenize
OpenAI PlatformOpenAI Platform organization settingsCompletions usage and cost reports, other usage reports, the member directory, and API key metadata. This feeds Platform Usage.
OpenAI AnalyticsOpenAI Admin Console (ChatGPT Enterprise)Codex analytics, and reading and changing per-person budgets
Compliance API keyOpenAI Admin ConsoleRead access to Codex and ChatGPT compliance logs

Add the OpenAI Platform key

An OpenAI organization owner must create this key. It must be an organization Admin API key, not a project key.

  1. Open Admin API keys in OpenAI Platform.
  2. Choose Create admin key. Set a name and expiration.
  3. Copy the key.
  4. In Tokenize, go to Settings → Providers. In the OpenAI section, open OpenAI Platform, paste it into API key, and click Save.

Add the OpenAI Analytics key

A ChatGPT workspace admin must create this key. You also need your Workspace ID.

  1. Open Credentials in the OpenAI Admin Console and create a workspace Admin key with Custom permissions.
  2. Set these permissions:
    • Enterprise analytics API: Read
    • Codex analytics API: Read (keep during the transition)
    • Usage limits: Write
  3. Copy the key.
  4. Copy the Workspace ID from your ChatGPT Admin workspace settings.
  5. In Tokenize, open OpenAI Analytics, paste the key into API key and the ID into Workspace ID, then click Save.

OpenAI's setup documentation has more detail.

Tokenize checks read access when you save. Write access to budgets is confirmed only when someone changes a budget, so the access check shows "Not yet verified. We will report the result when you change a budget." until then. See Budgets.

If the key can read Codex analytics but not usage limits, Tokenize still saves it with the unverified badge. Codex usage comes in, but budgets don't work, and Budgets lists the key as Needs spend limit access. To fix it, create a key with the permissions above and save it again.

Update an existing OpenAI Analytics key

OpenAI is replacing the Codex analytics API with the Enterprise analytics API. A key created before this change can still read Codex usage, but it needs the new permission to keep working after the switch. Until Tokenize has confirmed that permission, the OpenAI Analytics section shows one of these messages:

  • "Access to the new usage reporting API is not confirmed." Tokenize hasn't checked the new permission on this key yet.
  • "Update permissions: OpenAI denied access to the new usage reporting API." The key doesn't have Enterprise analytics API set to Read.

The message asks you to give the key Enterprise analytics API set to Read before December 15, 2026. You don't need to revoke the current key first. Either path works:

  • Add the permission to the saved key. In the OpenAI Admin Console, edit the key and set Enterprise analytics API to Read. Then click Check again in Tokenize. Tokenize re-runs its access check with the stored key, since OpenAI never shows a key's secret again. If the check passes, the access results show "New usage reporting permission: Available" and the message goes away. If it says "Key not accepted. Check the key and its permissions.", the saved key stays exactly as it was.
  • Create a new key. Follow the steps above, then paste the key and Workspace ID into the form under the message and click Update key.

Once an OpenAI Analytics key is saved, a Codex credit price section appears in the same group. See Set your Codex credit price.

Add the Compliance API key

A ChatGPT workspace owner must create this key.

  1. Open Credentials in the OpenAI Admin Console and choose Create admin key.
  2. Set this permission: Compliance logging platform > Read.
  3. Copy the key.
  4. Copy the Workspace ID from your ChatGPT Admin workspace settings.
  5. In Tokenize, open Compliance API key, paste both, and click Save.

OpenAI's guide to managing Admin keys has more detail.

When you save, Tokenize checks three kinds of logs: Codex logs, ChatGPT conversation logs, and ChatGPT workspace agent logs. A key that can read at least one of them works, and Tokenize reads only the kinds the key can reach. The panel shows a line for each, so you can see which ones the key can't read.

If none of the checks pass, Tokenize still saves the key with the unverified badge and says "Key saved. Some permissions couldn't be confirmed." Create a key with the permission above and click Replace.

After you save

Tokenize checks the key with OpenAI before storing it. The panel then shows the last four characters of the key, the Workspace ID if there is one, a status badge, when the key was last checked, and the result of each access check. See Provider key errors for what each status and message means.

To disconnect a key, click Revoke (or Remove for the Compliance API key). Data Tokenize already read stays. The source stops being read.