01

Before creating a key

Confirm the selected Verity project loads and supports Groq. A provider setup cannot fix a wrong loader, missing dependency, inactive Bedrock pack, or absent entity. Keep a clean working project baseline.

02

Create and store the key

Create the credential in GroqCloud, copy it once, and enter it only through the selected project's documented local configuration or command. MMB Guide never accepts or validates the key.

03

Verify configuration

Use the project's status/config screen or command to confirm Groq is selected, then send one short text prompt. Record the returned status code or exact redacted error before changing model or credential.

04

Error map

Groq documents standard API status codes.

ErrorMeaningAction
400Request/configuration problemReview model and request fields
401Missing or invalid authenticationRe-enter local key; revoke if exposed
403Permission/model restrictionCheck project permissions
404Endpoint or model unavailableUse a valid current model
429Rate limit reachedWait; check RPM/TPM/RPD limits
500/502/503Provider-side failureRetry later without rotating a valid key
05

Rate limits

A 429 can be triggered by requests per minute/day or tokens per minute/day. Check the account's current Limits page because limits vary by plan and model. Repeated rapid retries can extend the problem.

06

Key exposure response

If a key appears in chat, a screenshot, public log, Git repository, or shared server config, revoke it immediately in GroqCloud and create a replacement. Deleting the message alone does not invalidate the credential.