lolcreds

Public credential defaults and exposure patterns for authorized security testing.

Cohere

CohereAI API1 credential

Credentials1 documented
01

API Key

cohere / api-key

Cohere API keys authenticate requests to Cohere model APIs. Cohere's API reference states that requests must pass an Authorization header in the shape BEARER [API_KEY].

user definedsecretAPI key

Looks like

example
example

Cohere API token shape from public scanner rules; use with Cohere env/header/source context to avoid generic 40-char false positives

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Location

environment
CO_API_KEY, COHERE_API_KEY

Official/SDK Cohere API key environment variables

http header
Authorization

BEARER API key header used by Cohere API calls

source code

apps, search/rerank pipelines, notebooks, committed .env files

secret store

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

logs

HTTP client logs, gateway logs, and request dumps with Authorization headers

config file
cohere.yaml, cohere.json, notebook.ipynb

Product-local Cohere app/notebook configuration files; generic .env belongs to common scanner surfaces

Notes

Cohere keys are opaque bearer credentials with no reliable public prefix in the referenced docs. Embedding and rerank workloads often put them in data-processing notebooks and batch jobs, not only in web services.

Scope

Authorized use

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