/Integrations
v1.2OpenAI
Validate OpenAI API keys and manual credit-balance readiness.
Integration
OpenAI
Confirms API key validity through stable APIs.
AI features fail at the worst moment when the key is revoked, billing is disabled, or credits hit zero—often discovered only when the first paying user triggers a completion. PreFlight calls a stable OpenAI endpoint to validate the key and surfaces billing guidance so you confirm credits in the dashboard before launch.
Requirements
- OpenAI API key with access to the models your app uses
- Billing enabled on the OpenAI account (manual dashboard confirmation recommended)
Billing is manual
PreFlight validates key authentication but cannot read your OpenAI balance. Keep at least $5 in credits or an active payment method before opening AI features to customers.
What PreFlight checks
| Probe | What it proves |
|---|---|
| API auth | The key authenticates against a stable OpenAI API endpoint. |
| Key scope | The key is active and not revoked or expired. |
| Billing reminder | Results include guidance to confirm credits in the OpenAI dashboard. |
| Response metadata | Safe status and latency are recorded without logging the key. |
Failure guidance
| Symptom | Fix |
|---|---|
| Invalid API key | Create a new key in OpenAI → API keys and update PreFlight and your deployment env. |
| Insufficient quota | Enable billing and add credits in the OpenAI dashboard. |
| Model access denied | Confirm your key's organization has access to the models your app calls. |
| Rate limited | Reduce burst traffic or request a limit increase before launch traffic. |
Dashboard setup
- Open Integrations → OpenAI in your PreFlight project.
- Paste the API key used by your production or staging backend.
- Confirm billing and credits in the OpenAI dashboard.
- Run Pre-Flight Check and store the key only in server-side secrets.