HuntBee Framework
AI Settings
Configure OpenAI, Gemini or Claude through the Framework for HuntBee AI-powered features.
OptionalComponent 4.1.0Difficulty: Moderate
Configure one supported AI provider here. SEO Suite AI Content uses this shared Framework connection.
Start with one provider
You do not need to configure every AI provider. Choose the service you already use, enter its API key, enable it and test the connection.
Choose provider
Enter API key
Choose model
Save
Test Connection
Use AI Content
Shared AI settings
| Setting | What it means | Recommended for beginners | Change it when… |
|---|---|---|---|
| Default Provider | Which enabled provider HuntBee uses when a Suite does not explicitly request another one. | Choose the one provider you intend to use most. | You want a different default provider. |
| Provider Status | Turns that provider connection on or off. | Enable only providers you have configured and tested. | You stop using a provider or temporarily want to prevent calls. |
| API Key | Secret credential issued by the AI provider. It is stored in OpenCart settings and should never be public. | Enter the provider key, save, then test. | The provider rotates/revokes your key. |
| Model | The AI model used for requests. The Framework lists currently supported/recommended choices for your installed version. | Use the current recommended general model shown in the Framework unless you have a reason to choose another. | You need a different speed/cost/quality balance. |
| Reasoning | Where the selected model supports it, controls how much internal reasoning effort is requested. | Medium is a balanced starting point. | Your chosen model supports it and a task benefits from a different effort. |
| Verbosity | Where supported, controls how concise or detailed model output should be. | Medium. | Your content workflow consistently needs shorter/longer output. |
| Max Output Tokens | Optional cap on generated output. Blank/0 lets the provider/model default apply; Claude uses a safe fallback when needed. | Leave blank/0 at first. | You specifically need to limit response size/cost. |
| Temperature | Optional creativity/randomness control, only for compatible models. | Leave blank/default unless you understand your model behaviour. | A compatible model and workflow needs more/less variation. |
| AI Logging | Records safe diagnostic information without logging secrets. | Keep enabled while setting up or troubleshooting. | You have a reason to reduce diagnostic logging after stable use. |
Test Connection
The test sends a very small request using the currently entered configuration. A successful test confirms that HuntBee can authenticate and receive a response. It does not guarantee that every future prompt will succeed, because provider limits, model availability and billing can change.
Cost and privacy
- AI provider usage can create charges on your provider account. HuntBee does not control the provider’s pricing.
- Only send catalog/business data you are comfortable processing through the provider you selected.
- Never paste API keys into public screenshots or support forums.
- Use AI Content preview/manual generation before enabling automatic queueing.
Explore HuntBee Suites