Zactonz AI Connector for Groq
v1.0.0Groq connector for the WordPress AI Client. Very low latency inference on GroqCloud, with every model on your account discovered automatically.
Installation & setup
Install the plugin#
The plugin has been submitted to the WordPress plugin directory. Once it is listed there, go to Plugins › Add New, search for Zactonz AI Connector for Groq and click Install Now, then Activate. WordPress also links there directly from Settings › Connectors when it needs a connector that is not installed yet.
Until then, or to install manually: download the zip from the Download button above, go to Plugins › Add New › Upload Plugin, choose the zip and activate it. The plugin folder is wp-content/plugins/zactonz-ai-connector-for-groq/.
Connect to Groq#
- Create an API key in the GroqCloud console.
- Go to Settings › Connectors and paste the key into the Groq connector.
- Go to Settings › Groq to review the discovered models and choose a default model per capability, a reasoning effort for the default text model, and the request timeout.
The key is stored in the option WordPress registers for the connector, so the Connectors screen and the connector's own settings screen always show the same credential.
Keep the key out of the database#
Define GROQ_API_KEY in wp-config.php, or set an environment variable of the same name. When either is present the connector uses it, the settings field is disabled, and nothing is written to the database.
define( 'GROQ_API_KEY', 'gsk_…' );
Use a proxy or private gateway#
Settings › Groq has an API base URL field. Leave it empty to use https://api.groq.com/openai/v1, or point it at a gateway that speaks the same API.
Check the connection#
Tools › Site Health includes a connectivity test for Groq, which runs in the background so it never holds the screen open. Settings › Groq has a diagnostics button that reports the endpoint, HTTP status, latency, the number of discovered models, any configured defaults missing from the current catalogue, and the AI Client version. The key never appears in the report.