Deepgram

PASS consensus from 3 PASS.

The linked key guide and pre-recorded guide provide one account-to-key-to-cURL path for remote or local audio. One linked chain runs from signup to key to a runnable curl call against https://api.deepgram.com/v1/listen?model=nova-3&smart_format=true, with no guessing required. One clear path: create account via Console, get API key, then follow the pre-recorded audio guide with cURL or SDK examples.

PARTIAL consensus from 3 PARTIAL.

The plan tables give per-region caps, but they state 50 pre-recorded requests where the pre-recorded guide states 100. The rate limits reference gives a complete per-plan, per-region, per-model table, but the pre-recorded guide states 100 concurrent pre-recorded requests where the reference states 50 on every self-serve plan and region. Pre-recorded page says 100 concurrent requests but the API Rate Limits page says 50 for Nova-3 pre-recorded on Pay as You Go. Pages contradict each other.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The concurrency guide names the cause and recommends queues and backoff, but the errors page also defines 429 by request volume over time. The error reference names the payload and recommends exponential backoff, but its status-code list calls 429 a per-time-window limit while the concurrency guide denies any per-time-window limit, and the reference's own rate-limit link points at a #rate-limits anchor that no longer exists on the redirected pre-recorded page. Cause named, response format shown (TOO_MANY_REQUESTS error code), and exponential-backoff retry recommended with link to dedicated guide.

PASS consensus from 3 PASS.

The callback guides document the POST receiver, Listen request, asynchronous response, retries, and Basic Auth as the reliable origin check. The page documents the callback parameter, the permitted ports and protocols, the POST delivery, the ten-retry policy at 30 second intervals, and both authentication methods, including the caveat that dg-token is not guaranteed on every request. Full callback path documented: query parameter, server setup, retry behavior (10 attempts at 30s intervals), and two authentication methods (Basic Auth and dg-token header).

PASS consensus from 3 PASS.

The home page links the official SDK, and the guide provides installation plus a complete binary-audio example matching the REST local-file form. pip install deepgram-sdk python-dotenv plus the DeepgramClient example uses the same model=nova-3 and smart_format=true parameters as the curl form on the same page, though /docs/python-sdk redirects to the home page and the only Python SDK link is to GitHub. Official SDK on GitHub with clear README, pip install, and minimal working examples for URL and file transcription that match the API form shown in the developer docs.