What was decided
The founder missed part of a call with Acme. She asks Memtro what was decided. It finds the meeting she organised, reads tl;dv's AI notes by topic, and answers with the summary of each topic and who was invited.
Ask what was decided in a tl;dv meeting and exactly who said what.
Connect tl;dv with an API key and Memtro reads the meetings the key's user organised on Zoom, Meet or Teams, with time, length and invitees, their transcripts with timestamps, and tl;dv's AI notes by topic. Meetings merely shared with you are not read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can import a recording from a public link as a new meeting for tl;dv to transcribe and note. Each import uses one of the account's daily imports and cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right tl;dv tool, reads what it needs, and answers with the source cited.
These tools change something in tl;dv. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once tl;dv is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What was decided in the Acme call on Thursday?
What exactly did Priya say about pricing in yesterday's meeting?
Which external meetings did I have last week?
Summarise the topics from the Northwind kickoff
Import the recording of the Globex workshop from this link so it gets a transcript
The founder missed part of a call with Acme. She asks Memtro what was decided. It finds the meeting she organised, reads tl;dv's AI notes by topic, and answers with the summary of each topic and who was invited.
Ben Carter recorded an in-person workshop with Globex on his phone and asks Memtro to bring it into tl;dv. Memtro imports the file from the link he shares as a new meeting under his account, and tl;dv transcribes it and writes notes, so the team can ask about it later like any other call.
The teams that lean on tl;dv most, a question each of them asks, and what they connect beside it.
A record in tl;dv is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
tl;dv's API needs a Pro, Business or Enterprise plan and reads only meetings the key's user organised
In tl;dv open Settings → Personal settings → API keys, create a key and copy it
In Memtro open Connections → tl;dv, paste the API key and connect
Ask what was decided in your last customer call
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The tl;dv tools are the same everywhere.
Only when you ask, and only what it has been granted: import a recording from a public URL as a new tl;dv meeting, to be transcribed and noted (uses the daily import quota). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. tl;dv's API needs a Pro, Business or Enterprise plan and reads only meetings the key's user organised.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time