Agent skill · security · jeremylongshore
deepgram-security-basics
Apply Deepgram security best practices for API key management and data
Why this skill is useful
Provides specific security practices and code examples for managing Deepgram API keys and data protection that the AI wouldn't reliably generate on its own.
What it needs
Requires deepgram account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Deepgram Security Basics Prerequisites A data classification and consent decision for the audio/transcript workload. Scoped project credentials in the approved secret manager, an owner, and an incident/revocation route. Examples Use a development credential and a licensed non-sensitive audio fixture to verify the integration, logging only an opaque request ID and outcome. If recordings, transcripts, or keys are exposed, restrict access, revoke credentials where applicable, and follow the organization’s incident process before continuing. Overview Security best practices for Deepgram integration: scoped API keys, key rotation, Deepgram's built-in PII redaction feature, client-side temporary keys, SSRF prevention for audio URLs, and audit logging. Security Checklist [ ] API keys in environment variables or secret manager (never in code) [ ] Separate keys per environment (dev/staging/prod) [ ] Keys scoped to minimum required permissions [ ] Key rotation schedule (90 days recommended) [ ] Deepgram redact option enabled for PII-sensitive audio [ ] Audio URLs validated (HTTPS only, no private IPs) [ ] Audit logging on all transcription operations Instructions Step 1: Scoped API Keys Create keys with minimal permissions in Console > Settings > API Keys: Step 2: Deepgram Built-in PII Redaction Step 3: Temporary Keys for Client-Side Step 4: Key Rotation Step 5: Audio URL Validation (SSRF Prevention) Step 6: Audit Logging Output Scoped API keys per service/environment Built-in PII redaction via redact parameter Temporary keys for client-side (browser/mobile) Key rotation with validation and cleanup SSRF-safe audio URL validation Structured audit logging Error Handling Issue Cause Solution ------- ------- ---------- 403 after scoping Key missing required scope Add scope in Console (e.g., listen) Temp key expired TTL too short Increase timetoliveinseconds Rotation broke service New key not propagated Use overlap period — both keys active Redaction missed PII Wrong redact option …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/deepgram-security-basics