# Authentication and keys

Create, use and rotate your dataset keys.

## Get a key

[Verify your email](https://gloom.sh/datasets/console), [choose a plan](https://gloom.sh/datasets/console/billing), then [create a key](https://gloom.sh/datasets/console/keys). Payment confirmation starts the plan. Copy the key once; only its hash is stored.

## Send the key

```bash
export GLOOM_DATASETS_KEY=gds_...
curl https://api.gloom.sh/v1/gpu/prices \
  -H "Authorization: Bearer $GLOOM_DATASETS_KEY"
```

Keep keys server-side. `x-api-key` also works; `Authorization` takes precedence.

## Key format

Use `gds_`. Gloom Pro (`gloom_mcp_`) and News (`gloom_news_`) keys return `401 wrong_key`; other invalid keys return `401 invalid_key`. Dataset keys also read the News API at no credit cost.

## Rotate or revoke

Create a replacement, update your environment, then [revoke the old key](https://gloom.sh/datasets/console/keys). Revoked or lost keys cannot be recovered.

[Limits by plan](https://gloom.sh/datasets/docs/credits#limits-by-plan).

- [Previous Quickstart](https://gloom.sh/datasets/docs/quickstart)
- [Next Credits and limits](https://gloom.sh/datasets/docs/credits)