Deepgram API keys

• trufflehog 3.97.4
• betterleaks
• Reference 1
• Reference 2
• Reference 3
• Reference 4
• Reference 5
• Reference 6
• Reference 7

Context-gated arrival family (#384, product redact-secret#868; research #789). No Deepgram page or SDK code states a prefix, length or alphabet: the docs' 32-hex example is an ascending-digit placeholder (1234567890abcdef twice) that the create-key reference gives to both the key and its id. TruffleHog 3.97.4 (keyword deepgram, [0-9a-z]{40}) and betterleaks ([a-f0-9]{40}) agree on 40 characters, and one community post reports a working key of length 40; the tools disagree on whether the alphabet is hex or base36. The contract freezes the hex intersection and asserts nothing on any other letter, so no alphabet or case twin is authored. The value is recognised only beside a same-line deepgram name, host or SDK constructor, so its positives score as project policy. A bare 40-hex run is indistinguishable from a Git SHA-1. The api_key_id shares the key's shape in the docs and is a public lookalike; the temporary-key JWT from /auth/grant is a bearer-path credential, not this family.