OpenAI ChatGPT Enterprise connector

Connect Claresia to OpenAI ChatGPT Enterprise. End users invoke skills as Custom GPTs in the ChatGPT Enterprise app or web.

Prerequisites

ChatGPT Enterprise tier (Compliance API + admin Custom GPT controls require Enterprise; Plus/Team won’t work)
An OpenAI organization owner to mint the Compliance API key
Zero-retention enabled (default for Enterprise tier)

Part 1 — Generate the Compliance API key

Sign in to platform.openai.com as the organization owner.
Settings → API → Admin keys.
Create new admin key → Compliance scope. Name: claresia-{tenant_slug}.
Copy the key (shown once).

Part 2 — Connect in Claresia

In Claresia Onboarding Portal, click Connect LLM (Step 6) → pick OpenAI ChatGPT Enterprise.
Paste your Compliance API key + your OpenAI Organization ID (visible at platform.openai.com/settings/organization/general).
Click Test connection — Claresia calls GET https://api.openai.com/v1/organization/audit_logs to confirm.

Part 3 — Skill publish — automated where possible, manual upload elsewhere

Automated path (default for Enterprise tenants)

Claresia transpiles each Skill IR into an OpenAI Custom GPT bundle:
- System prompt
- Tool definitions (functions)
- Knowledge files (if the skill ships with reference material)
POSTs to the OpenAI admin API to create the GPT under claresia-{tenant_slug}-{skill_id}
Sets workspace ACL to your archetype groups
End users see the GPT in their ChatGPT Enterprise sidebar within ~2 min

Manual-upload fallback

For tenants without API publish enabled:

Command Center → Distribution → OpenAI → Export
Download per-skill ZIP bundle + a CSV manifest
Upload via ChatGPT Enterprise admin → Custom GPTs → Bulk import
Workspace ACL applied via the same UI

Part 4 — Telemetry ingest via Compliance API

Claresia polls OpenAI’s Compliance API every 60s:

GET https://api.openai.com/v1/organization/audit_logs
  ?event_types=gpt.invoked,gpt.failed
  &since=<last_seen_ts>

For each event tagged claresia-*, we normalize into fn_telemetry_event and write to the Hub.

End-user experience inside ChatGPT Enterprise

The user opens ChatGPT Enterprise → sidebar shows their entitled Custom GPTs:

claresia-dainese-incident-postmortem
claresia-dainese-prd-review
claresia-dainese-pipeline-hygiene

They click one, ChatGPT prompts for parameters as a structured Adaptive Card-equivalent (ChatGPT renders Markdown with form-like inputs), runs the skill, returns the reply with the standard footer:

[skill output body]

Claresia · Incident Postmortem · $0.04 · 2.3s · View record

Hub emission

ChatGPT Enterprise’s Custom GPT framework supports function calling. Claresia injects a claresia.emit_hub_record function into every GPT’s tool list. The model is instructed to call this function with the output payload — the function body is hosted at https://api.claresia.com/hub/v1/records (or the customer-cloud equivalent in Mode C).

Common gotchas

Symptom	Cause	Fix
Custom GPTs don’t appear	Manual-upload required for this org	Use the Export → Bulk Import flow
Telemetry missing	Compliance API not enabled (org < Enterprise tier)	Upgrade to Enterprise; or fall back to per-user audit export
Hub records missing	`emit_hub_record` function call refused by user	The GPT system prompt explicitly tells the model to always call it; if user disables, no Hub record is created (governance event written instead)
`401` on publish	Admin key is not Compliance scope (just regular Admin)	Re-mint with Compliance scope