KeyKeeperGroq
How an agent gets a Groq key through KeyKeeper, what to choose on console.groq.com, and how KeyKeeper verifies it.
| Template id | groq |
|---|---|
| Field | groq-api-key → GROQ_API_KEY · secret |
| Key looks like | whether it can be viewed again is unconfirmed |
| Created at | console.groq.com |
| Verified by KeyKeeper | GET https://api.groq.com/openai/v1/models — lists available models |
| Template checked | 2026-09-15 |
What the agent does
keykeeper providers show groq
keykeeper save --provider groq --from-clipboard --create --purpose "what this task does"
keykeeper run -c groq -- <your command>--provider groq fills in the credential id and the field. The environment
variable is the one Groq's own tools read, so nothing has to be mapped.
What only you can do
Sign in to GroqCloud
Choose the project
Create an API key
Copy the key, then approve the save in KeyKeeper's window.
What to choose
Create the key inside a project dedicated to this workload; project limits are the isolation boundary.
The agent is told the same thing. It opens the page for you and says what to pick; it never logs in, passes 2FA or pays on your behalf.
What KeyKeeper checks
- Before writing: the value must look like a Groq key (whether it can be viewed again is unconfirmed). A wrong paste is refused before anything is stored, and the agent is told why — without the value.
- After saving: KeyKeeper itself sends
GET https://api.groq.com/openai/v1/modelswith the key in theAuthorizationheader (lists available models). The agent receives accepted, rejected or could not reach — never the value.
Rotation and expiry
No universal expiry policy was confirmed for this credential type. Record the date shown by the provider, or leave it unknown. Rotate or revoke at console.groq.com.