OpenAI Account, API, and Project Settings
SmartSite Assistant uses a regular OpenAI API key for chat, model discovery, translation, metadata generation, files, and vector stores. Analytics can additionally use an organization Admin API key and Project ID.
The regular API key is the server-side credential used for normal SmartSite work: listing models, answering conversations, generating translations and metadata, and managing vector-store files. The Admin API key serves a different purpose—it allows organization-level usage and cost reporting. Keeping those roles separate helps you grant only the access the website actually needs.
The practical starting point is to create a scoped regular api key in the intended openai project. Continue through the workflow until you use the reveal buttons only in a private environment and hide the value again, then use the field notes below to understand which choices affected AI output and which only changed delivery, access, or presentation.
What this feature does and when to use it
Section titled “What this feature does and when to use it”Configure credentials after creating them in the OpenAI platform and before creating a working assistant or knowledge store.
Use this feature in the following situations:
- You are connecting a new WordPress installation to the intended OpenAI project.
- Chat works but organization usage/cost cards need separate administrator credentials.
- You are rotating a credential and need to verify every plugin feature that depends on it.
Where to find it
Section titled “Where to find it”Before you begin
Section titled “Before you begin”- SmartSite Assistant is installed and activated.
- You are signed in with an account that can manage WordPress options.
- An OpenAI API account with billing and project access appropriate to your organization.
- A secret-handling process that keeps credentials out of email, screenshots, and source control.
Set it up step by step
Section titled “Set it up step by step”- Create a scoped regular API key in the intended OpenAI project.
- Paste it into API Key and save.
- Only if organization usage/cost analytics is required, add an Admin API Key.
- Optionally enter a Project ID to filter usage and cost analytics.
- Save, then open Assistants and confirm the model list can load.
- Use the reveal buttons only in a private environment and hide the value again.
Fields, controls, and important values
Section titled “Fields, controls, and important values”These values decide whether WordPress can make the right kind of request to the right OpenAI account. They do not make an answer more accurate by themselves; they make chat, translation, metadata generation, synchronization, and reporting available. A regular key powers the assistant, while the optional reporting credentials only affect usage and cost information.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| API Key | Required runtime credential. Stored as a WordPress option and submitted to OpenAI from the server. | “API Key” enables the external service rather than improving response content. Enter the matching provider value exactly, protect it like a password, and complete the relevant live test before assuming chat, reporting, or delivery is available. |
| Admin API Key | Optional organization-level credential used by OpenAI Usage & Costs analytics, not normal chat. | “Admin API Key” is only for organization usage and cost reporting; visitor chat continues to use the regular key. Its broader reporting access makes careful storage, masking, and dashboard permissions especially important. |
| Project ID | Optional filter for usage/cost requests. | “Project ID” must be the machine identifier or key from the owning system, not a similar display label. Mixing projects, accounts, profiles, or WordPress options can make the form look complete while returning empty or unrelated data. |
| Active Assistant ID | Read-only local assistant ID managed from the Assistants tab. | “Active Assistant ID” links this setting to one specific external or stored resource. Verify the account and surrounding characters before saving, because an identifier can be syntactically valid yet belong to the wrong project, assistant, phone, or option. |
How to confirm it is working
Section titled “How to confirm it is working”Judge OpenAI Account, API, and Project Settings where its effect is actually consumed—by the administrator, visitor, model, or connected service. The expected result above is more useful than a green badge because it describes the behavior the configuration was meant to produce.
Practical example
Section titled “Practical example”Use a regular project key for a production website; add the Admin key only for administrators who need the organization usage dashboard.
Recommended practice
Section titled “Recommended practice”- Change one part of OpenAI Account, API, and Project Settings at a time and keep a short record of the previous value and test result.
- Verify the saved result in the screen, visitor session, or connected service that actually consumes the setting.
Important warnings
Section titled “Important warnings”Common problems and focused checks
Section titled “Common problems and focused checks”| Problem | What to check and what to do next |
|---|---|
| The key is saved but models or requests fail. | Check that the key is active, belongs to the intended project, has API access and billing, and was copied without spaces. |
| OpenAI Account, API, and Project Settings is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Separate credential, project, model, and network failures before changing assistant content. |
| A change on OpenAI Account, API, and Project Settings does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Separate credential, project, model, and network failures before changing assistant content. |
Screen reference
Section titled “Screen reference”- Capture
- Show the OpenAI API tab with both key fields masked, a sanitized Project ID, and the active assistant ID area.
- Show
- API Key, Admin API Key, Project ID, Active Assistant ID, Save button
- Viewport
- Desktop, 1440 × 900
- Annotate
- Use numbered callouts only for controls referenced in the procedure.
- Redact
- OpenAI keys, tokens, secrets, personal information, private URLs, IP addresses, and conversation text