Provider
OpenAIProduction Runs, structured orchestration, and general-purpose execution.
Workflow
Connect your own OpenAI API key for production-quality BYOK execution. opheli.ai uses your key server-side and does not show it again after save.
Guide summary
Connect your own OpenAI API key for production-quality BYOK execution.
Guide type
WorkflowThis guide reflects the current product workflow and surface ownership.
Sections
4Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Provider
OpenAIProduction Runs, structured orchestration, and general-purpose execution.
Mode
BYOKUsage is controlled by your connected Provider account.
Security
Server-side key useThe key is encrypted and not exposed in the browser after saving.
Guide section
Guide section
opheli.ai platform access is separate from model provider usage. When you connect a Provider key, your selected Provider may bill usage directly to your Provider account.
Budget tools inside opheli.ai are guardrails and estimates. Every cost display carries a confidence label: Verified by Provider, Estimated by opheli.ai, Pending Provider Sync, or Provider cost unavailable.
Always monitor the Provider dashboard directly for final billing, especially when a cost is estimated or unavailable.
Guide section
Warning
Do not assume limits, availability, retention, or data policies are identical across Providers. Verify the current provider documentation before critical use.
Guide section
What it is
OpenAI connected through BYOK.
When to use it
Production Runs, structured orchestration, and general-purpose execution.
Where to find it
Provider Vault.
What happens next
The Provider can be selected by Operators, Mission Copilot, and Runs through existing provider selection.
Common mistake
Assuming free-tier or low-cost routes provide reliable production capacity.
Related action
Open Provider Vault and add or rotate the key.