Niches · Meeting capture & meeting infrastructure

Record with participants told, and delete everything when asked

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
6companies, fit with a limit
13companies carry the tag
13share of the category's work
9first-hand accounts

What counts as done

The capture posts a visible notice in chat when it joins and starts recording, with text the deployer can set, can be removed mid-call by API, and a documented delete call removes recording, transcript and any debug media, with a retention setting per bot or account.

How agents ask for it: tell everyone the call is recorded, remove the notetaker from this meeting, delete the recording of that call, don't keep recordings longer than 30 days

Does the job, with a limit 6

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Attendee D
Attendee Labs, Inc.
send_chat_message lets the deployer post its own notice and leave removes the bot, but no automatic join notice exists, there's no retention setting, and delete_data works only after the bot has ended. The debug-recording leak (issue 960) was closed as fixed in September 2026. source
Circleback B
Circleback AI, Inc.
DELETE /meeting/{id} removes a meeting and workspace retention sliders delete recordings, transcripts and all data on schedule, but no recording notice in chat is documented and no API call removes the bot mid-call. source
Meeting BaaS B
SAS SPOKE
entry_message posts deployer text on join on all three platforms, leave removes the bot, and delete-data removes video, audio, transcripts, chat and screenshots. Retention is set by plan, not per bot, and the docs don't say what happens if the notice fails to post. source
MeetStream C
MeetStream Corp.
bot_message posts deployer text after joining, send_image can show a recording card, remove-bot ends it, recording_config.retention sets per-bot expiry (30 days default) and Delete Data removes recordings and transcripts. Chat can't post where the organiser disabled it, and no fallback is stated. source
Nylas Notetaker API BB
Nylas, Inc.
A default notice, replaceable by on_join and on_participant_join messages, posts minutes after joining while recording runs, and a failed post is skipped. leave removes the bot mid-call, retention_time sets 5 minutes to 30 days per bot, and media can be deleted. source
Recall.ai B
Hyperdoc Inc.
chat.on_bot_join and on_participant_join post deployer-set text, pinned on Meet, recording_config.retention sets per-bot expiry and delete removes media including backups. Media is kept indefinitely by default for newer accounts, and acc-41 found the notice best-effort. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Read AI E
Read AI, Inc.
The plans page names a retention policy that auto-deletes reports on paid plans, but recording notice, bot removal and delete calls couldn't be read. source

Doesn't do this job 6

Listings in the category that do something else, with the reason.

ListingWhy
Fathom C
Fathom Video Inc.
Fathom can email attendees to request consent, but the API has no call to remove the recorder mid-call or delete a recording or transcript, and no retention setting. source
Fireflies.ai B
Fireflies.AI Corp.
deleteTranscript removes a meeting, but the API has no recording notice, no call to remove the bot mid-call (only pause and resume) and no retention setting. source
Granola B
Granola, Inc.
An automated chat message and a watermark can tell participants, and transcripts auto-delete after a user-set period, but there's no API call to stop capture or delete a note or transcript, so an agent can't complete it. source
MeetGeek C
AIVISION PRODUCTS SRL
DELETE /v1/meetings/{id} exists, but the API has no recording notice, no call to remove the bot mid-call and no retention setting. source
tl;dv D
tldx Solutions GmbH
The API reference has no delete call, no notice setting and no call to stop a recording, so none of the success can be done by an agent. source
Zoom Realtime Media Streams (RTMS) C
Zoom Communications, Inc.
Zoom shows its own fixed disclosure and app notifications to participants and a REST call can stop the stream, but the notice text can't be set and there's no stored media or delete call; retention sits with the app. source

What stops agents finishing

  • consent flow left entirely to the deployer (acc-06)
  • notice posted best-effort, so a bot can record with no notice (acc-41)
  • media kept indefinitely by default (acc-07)
  • delete leaves debug recordings behind (acc-30)
  • upload import that needs a public link leaves recordings exposed (acc-55)

Around it

Before: meeting-capture.bot-to-transcript. After: agent-memory.delete-fact.

Where this comes from

Weight 13 of 100 in Meeting capture & meeting infrastructure: 9 of 56 accounts (acc-06, acc-07, acc-18, acc-19, acc-20, acc-30, acc-39, acc-41, acc-55); consent comes up in every general thread on notetakers

The same as data: /api/v1/use-cases/meeting-capture.notice-and-delete.json, or the MCP tool get_use_case with id meeting-capture.notice-and-delete. Other jobs in this category: /api/v1/niches?category=meeting-capture.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.