tl;dv API
tl;dv documents a v1alpha1 REST API with self serve keys, webhooks and an OAuth protected MCP endpoint. Access is gated to the Business plan and above, there is no sandbox, and the surface is still alpha versioned.
Frequently asked questions
tl;dv scores C+ on Supergood's API Report Card. tl;dv documents a v1alpha1 REST API with self serve keys, webhooks and an OAuth protected MCP endpoint. Access is gated to the Business plan and above, there is no sandbox, and the surface is still alpha versioned.
tl;dv has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
tl;dv is an AI meeting assistant that joins calls on Zoom, Google Meet and Microsoft Teams, records them, and produces transcripts, timestamped notes and summaries that teams search and share after the fact.
Sales and revenue teams, plus product, research and customer success groups inside small and midsize businesses that run most of their customer conversations on Zoom, Google Meet or Microsoft Teams. Teams install tl;dv against their calendar and conferencing accounts so it attends calls automatically, then review transcripts, AI notes and clipped highlights afterwards.
Public sources describe tl;dv as a widely marketed AI notetaker for Zoom, Google Meet and Microsoft Teams, but the accessible research surfaced no verified customer counts or market share figures, so the position here is qualitative rather than numeric.
Meeting recordings, full transcripts, AI generated notes and summaries, meeting metadata such as participants and dates, and imported external recordings.
The platform is a modern cloud native product built around current conferencing APIs, and its developer surface reflects recent work: a versioned REST path, webhook events with structured payloads, and a hosted MCP endpoint protected by OAuth 2.1 authorization code with PKCE and dynamic client registration against a Keycloak realm.
Third party API convention notes report 429 rate limiting with backoff behavior that the vendor does not officially document. A third party data export guide notes API access is gated behind the Business plan, leaving Free and Pro customers without programmatic export. Full sourced list under Sources below.
Common alternatives include Otter.ai, Fireflies.ai, Gong, Fathom, Avoma. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. There is no official tl;dv MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. tl;dv doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.