Skip to main content

Sending a key

  1. Someone on a team whose plan includes the API makes a key in the workspace, under Settings › API keys. It’s shown once.
  2. Keep it in the environment, as PODDATA_API_KEY. Never print it or write it to a file.
  3. Send it on every call, in the Authorization header:
A production key starts pd_live_ and works only on api.poddata.ai. A staging key starts pd_test_ and works only on staging. A key belongs to its team: everything it reads and writes is that team’s, and nothing it gets says what another team looks at.

What a plan allows

Every key, on every plan with the API: 120 requests a minute, then a 429 with Retry-After; 50 documents, transcripts and recordings read whole a UTC day; 20 quotes from one episode a UTC day. “A UTC day” starts at midnight UTC. A plan’s count is the team’s, whatever key or person asked. The last three limits are each key’s own, and an assistant signed in as a person is held to them as a key is.

When a call is refused for a limit

An ask PodData has taken already and not yet acted on, such as a read of a target that no source has run on yet, is answered again with again: true and isn’t counted twice.

What’s counted

Every call with a key is counted, refused ones too. GET /usage gives the team’s counts by day and kind:
The MCP tool get_usage gives the same.