tl;dv

Files and knowledge

tl;dv for AI agents. Managed auth, ready-made tools.

Find recorded meetings, read transcripts and notes, and import recordings in tl;dv on behalf of each of your users.

About tl;dv

With the tl;dv connector, your agent works with the meetings tl;dv recorded for each user. It can list past meetings, read a meeting’s transcript and notes, and import a recording from a link, using only the tools your project allows.

tl;dv is an AI meeting recorder and notetaker for Google Meet, Zoom and Microsoft Teams.

Tools

What your agent can do in tl;dv.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own tl;dv connection.

  • List meetings

    Read
    tldv_list_meetings

    List the user's recorded meetings.

  • Get a meeting

    Read
    tldv_get_meeting

    Get a meeting's details, such as its date and participants.

  • Get a transcript

    Read
    tldv_get_transcript

    Get the transcript of a recorded meeting.

  • Get notes

    Read
    tldv_get_notes

    Get the notes and highlights of a meeting.

  • Import a meeting

    Write
    tldv_import_meeting

    Import a meeting recording from a URL.

Control

Limits you can set.

You decide what your agent may do in tl;dv, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read meetings, transcripts and notes, and switch off tldv_import_meeting so it can never add a recording.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example notes but not full transcripts. A call outside them is refused.

Get started

Connect tl;dv
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect tl;dv

    Each end user authorizes their own tl;dv account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own tl;dv account, once.
    const connection = await agent200
      .user("user_123")
      .connect("tldv");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the tl;dv tools

    Name the user, the model and the tools. The model decides which tl;dv tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Summarize yesterday's product review meeting",
        tools: ["tldv"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own tl;dv account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in tl;dv, such as reading meetings, transcripts and notes. Users can revoke it later from their tl;dv account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the tl;dv connector and how to use it.

Agent brief
Connector: tl;dv, through Agent200. In code: "tldv".
What it does: Find recorded meetings, read transcripts and notes, and import recordings in tl;dv on behalf of each of your users.
Page: https://www.agent200.com/connectors/tldv/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on tl;dv's own page, through the authorization link Agent200 returns. Never ask a user for a tl;dv password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: tldv_list_meetings, tldv_get_meeting, tldv_get_transcript, tldv_get_notes. Write tools: tldv_import_meeting. Name "tldv" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/tldv/framework/claude/
   https://www.agent200.com/connectors/tldv/framework/chatgpt/
   https://www.agent200.com/connectors/tldv/framework/claude-code/
   https://www.agent200.com/connectors/tldv/framework/muse/
   https://www.agent200.com/connectors/tldv/framework/grok-bot/
   https://www.agent200.com/connectors/tldv/framework/openai-dots/
   https://www.agent200.com/connectors/tldv/framework/claude-duet/
   https://www.agent200.com/connectors/tldv/framework/hermes-agent/
   https://www.agent200.com/connectors/tldv/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/tldv.md

Guides

Use tl;dv with the AI you build on.

Step-by-step setup for tl;dv with a specific model, assistant or agent framework.

FAQ

tl;dv and Agent200, answered.

Who handles the tl;dv OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for tl;dv.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's tl;dv connection, never another user's. It cannot reach anything the user or tl;dv has not authorized.

Can I limit what my agent can do in tl;dv?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with tl;dv.
Your agent does the rest.

Your users connect their own tl;dv accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)