Check access without inference
The connection test reads Groq's documented model catalog with the encrypted project key. It does not send a prompt or generate tokens merely to prove the key can reach the project.
Connect one Groq project. Give each workload an approved model, an immediate spending limit, rate ceilings, and a fallback.
Test the exact Groq model, API shape, streaming behavior, rate-limit response, and unsupported Responses parameters before production approval.
AIGHQ_BASE_URL=https://api.aigatewayhq.com/v1
AIGHQ_API_KEY=from-your-workspace
AIGHQ_MODEL=company-approved-fastEach Groq-backed application uses the gateway URL, its scoped workload key, and a stable model alias. Administrators can change an eligible Groq model or API key centrally without distributing the Groq credential to every app.
Select Groq and enter a project-specific API key. The connection test reads the model catalog and does not generate tokens. Then map an eligible model to a stable alias.
Compatibility follows the provider's current published interface. Review the provider documentation before approving Groq for production.
Need the complete client-to-provider path? Follow the tested Codex CLI, AI Gateway HQ, and Groq setup