tl;dv (BYOK)

tl;dv (BYOK) — connector documentation

• MCP endpoint: https://byok-tldv.connectorbay.com/mcp
• REST API: POST https://byok-tldv.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-tldv.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own tl;dv API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-tldv.connectorbay.com/health · Tool schemas: https://byok-tldv.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-tldv · agent@connectorbay.com

What tl;dv (BYOK) is for

tl;dv (BYOK) lets an AI assistant read your own tl;dv data through the tl;dv API with a key you supply (API key). Read-only: 6 tools (list_meetings, search_meetings, get_meeting, get_transcript, get_meeting_notes, check_api_health). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to pasta.tldv.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by tl;dv. tl;dv and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "What meetings did tl;dv record this week?"
• "Find tl;dv meetings about the quarterly review"
• "Who attended the tl;dv meeting 6650f0c1a2b3c4d5e6f70811?"
• "What was said in the tl;dv meeting 6650f0c1a2b3c4d5e6f70811?"
• "Give me the tl;dv AI notes for meeting 6650f0c1a2b3c4d5e6f70811"
• "Is the tl;dv API reachable with my key?"

What it does

• list_meetings: List your tl;dv meetings, newest first, with title, date, duration, organizer and invitees. Up to 100 per page and at most 10,000 results in total, so narrow with a date range.
• search_meetings: Search your tl;dv meetings by words in the title.
• get_meeting: Get one meeting: title, date, duration, organizer, invitees, template and conference ID.
• get_transcript: Get the speaker-labelled transcript of a meeting as segments with speaker, text and start and end time in seconds. Only available once the transcript is complete.
• get_meeting_notes: Get the AI notes of a meeting: a markdown summary, the topics with their summaries and the structured note lines with timestamps.
• check_api_health: Check that the tl;dv public API is up and the key is accepted.

BYOK key

You bring your own tl;dv API key (https://tldv.io/app/settings/personal-settings/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to pasta.tldv.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Read-only. The API only returns meetings whose organizer is on a paid tl;dv plan. Transcripts and notes contain personal data from meetings.

Data sources

• https://doc.tldv.io/index.html (the API this connector calls, with a BYOK key)

Live from the tl;dv API (pasta.tldv.io) with a BYOK key; documentation: https://doc.tldv.io/index.html. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by tl;dv. tl;dv and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your tl;dv account.

Built for: Worldwide. Languages: English.

tl;dv (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What tl;dv (BYOK) is. tl;dv (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own tl;dv data: Read your tl;dv meeting recordings, transcripts and AI notes with your own API key. You bring your own tl;dv API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one tl;dv call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to pasta.tldv.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If tl;dv rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What tl;dv receives. The request we make on your behalf, including the key and the arguments, under tl;dv's own terms and privacy policy. tl;dv acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer tl;dv gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your tl;dv data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. tl;dv (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at tl;dv at any time to end all access.

Children. tl;dv (BYOK) is a general-audience service operated by the adult using the assistant, under tl;dv's own age rules.

Changes. We will post changes here with a new effective date.

tl;dv (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the tl;dv (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. tl;dv (BYOK) provides: Read your tl;dv meeting recordings, transcripts and AI notes with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own tl;dv credentials and only access data you are allowed to access. tl;dv's terms apply to your use of tl;dv; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by tl;dv. tl;dv and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data tl;dv returns, lightly trimmed; it may be incomplete, delayed or changed by tl;dv. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your tl;dv account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent tl;dv's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; tl;dv may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your tl;dv key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action tl;dv takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-tldv

tl;dv (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-tldv.connectorbay.com/mcp
• REST API: https://byok-tldv.connectorbay.com/openapi.json
• Live status: https://byok-tldv.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. tl;dv (BYOK) never asks for them.