AI providersStatus: Available
OpenAI
Use your own OpenAI API key for generation in this workspace.
What it enables in Codexa
- Store your own OpenAI API key encrypted in the workspace and test it from workspace settings before saving.
- Prepare the workspace for bring-your-own-key AI runs with OpenAI models (billed to your OpenAI account).
- test
- byok
Setup
Fields on the workspace connection form. Password-type fields are encrypted before storage and never shown again.
| Field | Type | Required | Example |
|---|---|---|---|
API key apiKey | secret | Yes | sk-... |
- Open Settings → Integrations in your workspace (requires the admin or owner role).
- Choose the provider, give the connection a name, and fill in the fields listed above. Secret fields are encrypted before they are stored and are never sent back to the browser.
- Click Test connection. Codexa makes a single read-only request to the provider to confirm the credentials work.
- Save. The connection is now available to projects in this workspace.
- Today the AI agent runs with the operator-level OPENAI_API_KEY or ANTHROPIC_API_KEY; routing runs through a workspace key is being wired up and is not active yet. When no key is configured at all, the AI panel shows a 'not configured' state.
Required permissions and scopes
- An OpenAI API key with access to the chat completions API. Keys are encrypted at rest and never returned to the browser.
Limitations
- Usage limits from your Codexa plan (requests and tokens) apply to every AI run, including runs with your own key once that routing is active.
- Fine-tuned models and assistants/threads APIs are not supported.
More in ai providers
View all- AI providersStatus: Available
Anthropic
Use your own Anthropic API key (Claude) for generation in this workspace.
- Test the connection from workspace settings before saving
- Bring your own API key for this workspace's AI runs
Connect OpenAI to your workspace
Create a free account, add the connections your project needs, and let the AI agent build against them.