Documentation · OpenAI API configuration
Connect OpenAI without exposing your API key.
Prepare API billing, create a dedicated key and store it through SitePublisher AI’s preview-first Credential Vault before generating your first article.
Your own OpenAI account · Separate API billing · Never share or publish the key
Before creating a key
Prepare your OpenAI API account
SitePublisher AI uses the OpenAI API rather than the ChatGPT website. API access, usage and billing are managed through your own OpenAI Platform account.
OpenAI Platform account
Sign in or create an account on the official OpenAI Platform. Use an account controlled by your business or the person responsible for API billing.
Open the platform ↗API billing
Add an API payment method or available balance as required by your account. A ChatGPT subscription alone does not provide API balance.
Open API billing ↗Current pricing
API charges depend on the models and usage. Review OpenAI’s current pricing instead of relying on a fixed amount shown in an older guide.
Review API pricing ↗Limits and alerts
Choose appropriate spend controls and alerts. A hard spend limit stops affected API traffic when the tracked spend reaches that limit.
Review limits ↗Dedicated project
When project management is available, use a project for SitePublisher AI. It makes usage, access and future key rotation easier to control.
Clear ownership
Keep recovery and billing access with the correct owner. SitePublisher AI cannot manage or restore an external OpenAI account for you.
Create the credential
Generate a dedicated secret API key
OpenAI uses API keys to authenticate requests. Create a separate key for SitePublisher AI so it can be monitored, replaced or revoked without affecting unrelated applications.
Open API keys
Sign in to the OpenAI Platform and open the API keys area for the project that will be used by SitePublisher AI.
Create a new secret key
Give the key a recognizable name such as SitePublisher AI. Do not reuse a key that is already embedded in another application.
Choose suitable permissions
A read-only key cannot create content. If you restrict permissions, allow the API operations required for text responses and image generation.
Create and copy once
Generate the key and copy the complete value immediately. OpenAI may not show the full secret again after you leave the creation screen.
Keep it private
Do not place the key in email, chat, screenshots, shared documents, source code, analytics tools or a public support request.
Move directly to WordPress
Paste the key into the SitePublisher AI Secret API key field, complete the protected save process and remove temporary unsecured copies.
SitePublisher AI
Preview and save the encrypted key
The save button remains unavailable until SitePublisher AI has validated an exact preview. The secret itself is not displayed in that preview.
Enter the key
- Open SitePublisher AI → Platform Settings
- Select the OpenAI API tab
- Paste the complete key into Secret API key
- Check that no leading or trailing space was copied
Build the preview
- Select Preview key change
- Review the Action and Storage rows
- Confirm the intended active source after saving
- Confirm that the key is not exposed in the preview
Save and verify
- Select Save encrypted key
- Check that GPT configuration says Configured
- Check that Encrypted key stored says Yes
- Note whether an approved external source has priority
Credential security
Understand what SitePublisher AI protects
The OpenAI key is a credential that can create billable API traffic. Treat it with the same care as other production secrets and limit who can manage WordPress settings.
Encrypted storage
The SitePublisher AI Credential Vault encrypts the key using AES-256-GCM and binds protection to the WordPress authentication keys.
No routine exposure
The stored key is not included in logs, PDF reports, normal page HTML or the change preview.
Explicit reveal only
Show stored is available only as a deliberate administrator action. Avoid revealing the key on shared screens or recorded sessions.
Replace and revoke
If the key may be exposed, revoke it in OpenAI immediately, create a replacement and save the new key through a fresh preview.
Do not send an OpenAI API key to SitePublisher AI, your hosting provider or another third party. Share only the non-sensitive error message and timing.
Verify the connection
Use a controlled first request
A stored key confirms configuration, but the first real API request also depends on billing, permissions, model access and the hosting connection.
Check the saved state
Confirm Configured, Encrypted key stored and the expected Active source on the OpenAI API Settings page.
Create a draft first
Use the Single Article guide and keep the first result in a review-first workflow. Inspect the content before any WordPress publication decision.
Open the first article guide →Review OpenAI usage
After a successful request, confirm usage in the OpenAI dashboard. OpenAI remains the source for actual external API billing.
Open API usage ↗Troubleshooting
Match the error to the correct account or website check
Keep the exact non-sensitive error message. Do not repeatedly create new keys until you know whether the issue is authentication, billing, permissions or connectivity.
Authentication, quota or rate limit
Open the OpenAI Platform and verify the selected project, key status, billing, current limits and usage.
- Confirm that the key has not been revoked
- Check for an incomplete or space-padded key
- Confirm active API billing or balance
- Review project spend and rate limits
- Check permissions when using a restricted key
Storage or connection problem
Use SitePublisher AI Health information and WordPress Site Health to identify local configuration or outbound connection problems.
- Confirm that encrypted key storage is available
- Check that WordPress authentication keys are present
- Ask the host whether outbound HTTPS is blocked
- Allow secure connections to api.openai.com
- Send Support no credentials or secret screenshots
Next guide
Create your first Single Article.
With OpenAI configured and the Website Profile saved, continue with a controlled article brief, review the generated result and keep the first publication decision manual.
OpenAI API FAQ
Common account and key questions
These answers explain the separation between OpenAI, ChatGPT and SitePublisher AI.
Can I use a ChatGPT subscription instead of API billing?
No. SitePublisher AI connects to the OpenAI API. API usage and billing are managed separately through your OpenAI Platform account.
Does SitePublisher AI receive my OpenAI password?
No. You connect a secret API key, not the OpenAI account password. Never enter your OpenAI password into SitePublisher AI.
Can I use a restricted API key?
Yes, provided it can create the text responses and image generations used by your workflow. A read-only key cannot generate content.
What should I do if the key is exposed?
Revoke it immediately in the OpenAI Platform, create a new dedicated key and replace the stored key through Preview key change and Save encrypted key.
Where can I see the actual OpenAI costs?
Use the OpenAI Usage and Billing pages for actual external API charges. SitePublisher AI analytics can help monitor workflow usage but does not replace the OpenAI billing record.
Official guidance
Keep account and pricing information current.
OpenAI can update its platform interface, limits and prices. Use the official OpenAI documentation and dashboard links on this page for the current account information.