Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

OpenAI

An OpenAI connector routes OpenAI requests through HYPR AgentPass™, from Codex CLI, other local agents and cloud agents. Each request is attributed, evaluated by policy and recorded.

Before You Begin​

  • An OpenAI account with API access
  • An OpenAI Admin API key, and the project ID the gateway serves
  • The gateway's public origin, which your agents point at

Create the Connector​

  1. Open All Connectors → Add Connector → AI Providers → OpenAI.
  2. Enter the Admin API Key and Project ID.
  3. Optional: Change the Base URL only if your OpenAI configuration requires a different value.
  4. Click Next.
  5. Choose the onboarding mode.
  6. Click Create Connector. The connector opens.

What the Overview Tab Shows​

The connector's Overview tab has these fields.

FieldMeaning
Name, EnabledThe connector's name. Enabled turns traffic on or off
EndpointThe upstream host and port (api.openai.com:443). Click Change to point at a private or regional deployment
Allow Channel connectionsLets agents use this gateway as a channel for real-time supervisor messaging. On by default. See Having Conversations with Your Agent
OpenAI Admin APIThe base URL, project ID and write-only admin API key. Click Update Key to replace the key. Used to sync the project's API keys into agent identities
Download Bash Setup, Download PowerShell SetupScripts that configure Codex CLI with the gateway's public origin as its base URL, and the built-in AgentPass MCP server. The script keeps the rest of the user's Codex configuration
Onboarding ModeWhat happens to an agent's first request. See Onboarding Mode
RoutesThe request paths the gateway forwards

Agents Tab​

Sync from OpenAI imports the project's API keys as agent identities, with a name, type, owner and status for each. Synced identities appear on the Agent identities page. See Agent identity.

Point an Agent at It​

Point Codex CLI at the connector in one of two ways:

  • Run the downloaded setup script on the developer's workstation.
  • Route Codex CLI through the Endpoint Guard, with no change on the agent side. See Routing and Observation.