tldv

Original：🇺🇸 English

Translated

tl;dv API for meeting recordings. Use when user mentions "tl;dv", "meeting recording", "meeting summary", or asks about call analysis.

4installs

Sourcevm0-ai/vm0-skills

Added on2026-05-03

NPX Install

npx skill4agent add vm0-ai/vm0-skills tldv

SKILL.md Content

View Translation Comparison →

Troubleshooting

If requests fail, run

zero doctor check-connector --env-name TLDV_TOKEN

or

zero doctor check-connector --url https://pasta.tldv.io/v1alpha1/health --method GET

How to Use

All examples below assume you have

TLDV_TOKEN

set.

Base URL:

https://pasta.tldv.io

API version:

v1alpha1

(alpha — endpoints may change before stable v1 release).

Authentication uses the

x-api-key

header (not Bearer).

Health Check

Verify API Connectivity

bash

curl -s "https://pasta.tldv.io/v1alpha1/health" --header "x-api-key: $TLDV_TOKEN" | jq .

Meetings

List Meetings

bash

curl -s "https://pasta.tldv.io/v1alpha1/meetings" --header "x-api-key: $TLDV_TOKEN" | jq '.results[] | {id, name, happenedAt, duration, organizer: .organizer.name}'

List Meetings with Pagination

bash

curl -s "https://pasta.tldv.io/v1alpha1/meetings?page=1&pageSize=10" --header "x-api-key: $TLDV_TOKEN" | jq '{page, pages, total, meetings: [.results[] | {id, name, happenedAt}]}'

Get Meeting by ID

bash

curl -s "https://pasta.tldv.io/v1alpha1/meetings/<meeting_id>" --header "x-api-key: $TLDV_TOKEN" | jq '{id, name, happenedAt, duration, url, organizer, invitees}'

Download Meeting Recording

Returns a 302 redirect to a signed download URL (expires after 6 hours). Use

-L

to follow the redirect, or omit it to inspect the URL:

bash

curl -s -I "https://pasta.tldv.io/v1alpha1/meetings/<meeting_id>/download" --header "x-api-key: $TLDV_TOKEN" | grep -i location

To download the recording directly:

bash

curl -s -L -o /tmp/tldv_recording.mp4 "https://pasta.tldv.io/v1alpha1/meetings/<meeting_id>/download" --header "x-api-key: $TLDV_TOKEN"

Import a Meeting

Write to

/tmp/tldv_request.json

:

json

{
  "url": "https://example.com/recording.mp4"
}

bash

curl -s -X POST "https://pasta.tldv.io/v1alpha1/meetings/import" --header "x-api-key: $TLDV_TOKEN" --header "Content-Type: application/json" -d @/tmp/tldv_request.json | jq .

Transcripts

Get Meeting Transcript

bash

curl -s "https://pasta.tldv.io/v1alpha1/meetings/<meeting_id>/transcript" --header "x-api-key: $TLDV_TOKEN" | jq '.data[] | {speaker, text, startTime, endTime}'

Get Full Transcript as Plain Text

bash

curl -s "https://pasta.tldv.io/v1alpha1/meetings/<meeting_id>/transcript" --header "x-api-key: $TLDV_TOKEN" | jq -r '.data[] | "\(.speaker): \(.text)"'

Highlights / Notes

Get Meeting Highlights

bash

curl -s "https://pasta.tldv.io/v1alpha1/meetings/<meeting_id>/highlights" --header "x-api-key: $TLDV_TOKEN" | jq '.data[] | {text, startTime, source, topic: .topic.title, summary: .topic.summary}'

Get Topic Summaries Only

bash

curl -s "https://pasta.tldv.io/v1alpha1/meetings/<meeting_id>/highlights" --header "x-api-key: $TLDV_TOKEN" | jq '[.data[] | .topic | select(. != null)] | unique_by(.title) | .[] | {title, summary}'

Guidelines

Authentication uses the

x-api-key

header, not

Authorization: Bearer

. Every request must include

--header "x-api-key: $TLDV_TOKEN"

.

The API is versioned at
```
v1alpha1
```
. This is an alpha API — endpoints and response formats may change.
All requests must use HTTPS. Plain HTTP requests are rejected.
API access requires the meeting organizer to have a Pro, Business, or Enterprise plan. Free plan organizers have no API access.
Meeting IDs are strings. Use
```
jq
```
to extract
```
id
```
fields from list responses.
Transcripts are only returned when processing is complete. If a meeting was just recorded, the transcript may not be available yet.
Download URLs from the
```
/download
```
endpoint expire after 6 hours.
Pagination: the meetings list returns
```
page
```
,
```
pages
```
,
```
total
```
, and
```
pageSize
```
fields. Use
```
?page=N
```
to navigate pages.
Use
```
<placeholder>
```
for dynamic IDs that the user must replace (e.g.,
```
<meeting_id>
```
).
Write request bodies to
```
/tmp/tldv_request.json
```
before sending.

tldv

NPX Install

Tags

SKILL.md Content

Troubleshooting

How to Use

Health Check

Verify API Connectivity

Meetings

List Meetings

List Meetings with Pagination

Get Meeting by ID

Download Meeting Recording

Import a Meeting

Transcripts

Get Meeting Transcript

Get Full Transcript as Plain Text

Highlights / Notes

Get Meeting Highlights

Get Topic Summaries Only

Guidelines