lolcreds

Public credential defaults and exposure patterns for authorized security testing.

GroqCloud

GroqAI API1 credential

Credentials1 documented
01

API Key

groq / api-key

GroqCloud API keys authenticate requests to Groq's OpenAI-compatible API. Groq's quickstart documents exporting the key as GROQ_API_KEY and sending it as a Bearer token in the Authorization header.

user definedsecretAPI key

Looks like

example
example

Groq API key form commonly seen in GroqCloud deployments

gsk_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Location

environment
GROQ_API_KEY
http header
Authorization

Bearer token used by Groq API calls

source code

scripts, inference services, notebooks, committed .env files

config file

.env, shell profiles, deployment manifests, local app config

secret store

CI/CD variables, cloud secret managers, hosted app settings

logs

HTTP client debug logs and request dumps with Authorization headers

Notes

Groq exposes OpenAI-compatible endpoints, so Groq keys are often placed in code paths originally written for OpenAI-style clients. Check both provider-specific GROQ_API_KEY variables and generic LLM gateway config.

Scope

Authorized use

LOLCreds helps map the credential surface of real products: known defaults, generated values, credential locations, and exposure patterns.