Happy Scribe
DOCS & KNOWLEDGE · FILES & DOCS
Transcriptions, subtitles, translations, and their AI summaries on their own key.
Connecting Happy Scribe in practice
Happy Scribe’s MeetingKit limits creation rather than reading: 100 new members an hour per workspace, 100 notetaker bots an hour, 1,000 pushed calendar events a minute, and 20 workspaces a day per API user with archived ones counted. Reads are not rate limited at all, and a 429 carries retry_in_seconds in the JSON body as well as in Retry-After.
Scopes that draw scrutiny
Authorization: <personal API key>The key is personal: requests act as your user and can reach any workspace you are a member of, so the blast radius is that person’s membership rather than a scope list.
Rate limits
- POST /members: 100 new members an hour per workspace, and members created by a pushed calendar event count against it too.
- POST /calendar_events: 1,000 pushes a minute per workspace.
- POST /bots: 100 bots an hour per workspace.
- POST /workspaces: 20 a day per API user, archived ones included.
- Reads are not rate limited. A 429 returns retry_in_seconds in the body and the same number in the Retry-After header.
Worth knowing
- Archived workspaces still count against the twenty-a-day creation limit, so an agent that provisions and tears down a workspace per customer runs out on the twentieth attempt.
- Member creation is implicit: pushing a calendar event for someone who is not yet a member creates one and spends the members-per-hour budget without a members call.
- The bare key is the canonical Authorization value but Bearer and Token prefixes also authenticate, case-insensitively, so a leaked key works from any client shape.
- Requests carry a happyscribe-version header, so behaviour is pinned per request rather than per account and two callers on one key can be on different API versions.
Checked against Rate limits (2026-09-29), Authentication (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Happy Scribe behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.