API keys
Synthetic keys for this demo. Changes stay until you reload.
| Key | Scope | Last used | Status | Actions |
|---|---|---|---|---|
Northstar · production gd-live-8F2L9X | Production | 2 min ago | Active | |
Playground · dev gd-test-7C1K2Q | Development | 1 hr ago | Active | |
Embeddings · batch gd-live-6B0J1P | Production | 5 min ago | Active | |
Legacy ingest (rotated) gd-live-4D7G8Y | Sandbox | 9 days ago | Revoked |
- Northstar · production
gd-live-8F2L9XActiveProductionLast used 2 min ago - Playground · dev
gd-test-7C1K2QActiveDevelopmentLast used 1 hr ago - Embeddings · batch
gd-live-6B0J1PActiveProductionLast used 5 min ago - Legacy ingest (rotated)
gd-live-4D7G8YRevokedSandboxLast used 9 days ago
Secrets appear only when created or rotated. The list retains key IDs, never reveals secrets.
Request share
Where the last 30 days of volume came from.
2.25M total
Northstar · production
1.84M · 81.8%
Embeddings · batch
396.4K · 17.6%
Legacy ingest (rotated)
12.1K · 0.5%
Playground · dev
482 · <0.1%
Total · 30d
2.25M
First request
Example request shape, not a live API endpoint.
request.shbash
curl https://api.gumdrop.example/v1/chat/completions \
-H "Authorization: Bearer $GUMDROP_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "model-4-5", "messages": [{"role":"user","content":"Hi"}]}'Replace the example endpoint and set GUMDROP_API_KEY to your saved secret.