AI Meeting Transcription Tools: 4 Patterns Compared (2026)

Updated October 2026: current meeting-bot API prices (Recall.ai, Skribby, Vexa, Nylas), the 2026 rulings and new suits against Otter, Fireflies and Granola, Granola on Android, Meet and Zoom APIs that export notes without a bot, and a new FAQ.

Why this matters

Short answer: AI meeting transcription turns a call's audio into a speaker-labelled transcript plus an AI-written summary. Every tool runs the same pipeline (capture, speech recognition, diarization, summary) and differs mainly in how it captures the audio: the platform's own AI (Zoom, Teams, Meet), a cloud bot that joins the call (Otter, Fireflies, Fathom), a bot-free desktop app (Granola), or an infrastructure API you build on (Recall.ai, $0.50 per recording hour in October 2026). Pick the capture pattern first, then the vendor.

Meeting transcription stopped being a novelty and became a category: the AI note-taking market was about $623 million in 2025 and crosses roughly $740 million in 2026, inside a broader AI-meeting-assistant market growing about 26% a year. If you run a product team, a sales org, or a video platform, two questions are now landing on your desk — "which note-taker should we standardize on?" and, increasingly, "should we build this into our own app instead of paying per seat?" This lesson answers both by giving you a single mental model — four capture patterns and one privacy rule — so a product lead can choose a tool without drowning in feature grids, and an engineer can see exactly where the build-versus-buy line falls. It sits in the LiveKit build series in this section: the earlier lessons show you how to build a transcription agent, and this one zooms out to the whole market around it.

The one thing that actually separates these tools

Open any "best AI note-taker" list and you get a wall of feature checkboxes: summaries, action items, CRM sync, speaker labels, chat-with-your-meeting. Almost all of them have almost all of it. The feature grid is not where the real decision lives.

The decision lives one layer down, in a question most buyer's guides skip: how does the tool get the audio in the first place? That single architectural choice — call it the capture pattern — determines three things you actually care about. It decides whether other people in the meeting can see that you are recording, which is a privacy and trust question. It decides what you pay and how, because a tool that runs on your laptop has a very different cost shape than one that runs a server for every call. And it decides whether the tool can ever live inside a product you build, or only sit beside your meetings as a separate app.

So this lesson is organized around capture, not features. Once you know the four patterns, every product on every comparison list snaps into one of them, and the right choice for your situation becomes obvious.

Figure 1. The four capture patterns. Every meeting-transcription product on the market is one of these four; the rest of their feature lists barely differ.

A 30-second definition of the job they all do

Before the patterns, the job. Every tool here runs the same three steps, and naming them keeps the rest of the lesson clear.

First, capture — getting the spoken audio out of the meeting and into the software. This is the step that differs the most, and it is the whole point of this lesson.

Second, speech recognition — turning that audio into text. The technical name is automatic speech recognition, usually shortened to ASR. This is a solved-enough commodity now; the same handful of engines (we cover them in the streaming ASR lesson) sit underneath nearly every product on the market, which is exactly why accuracy no longer separates them.

Third, understanding — two layers stacked on the raw text. One layer is diarization, a clumsy word that just means labelling who said which line, so the transcript reads "Maria: …" and "Sam: …" instead of one undifferentiated wall of words. The other layer is the summary: a language model reads the full transcript and writes a few paragraphs of recap plus a list of action items. When a buyer's guide says "AI meeting summary", this is the layer it means — a model writing prose on top of a transcript, not a separate kind of magic.

Hold those three steps in mind. The four patterns below are really just four different answers to step one.

Pattern 1 — The platform's own built-in AI

The simplest pattern is to use the transcription that your meeting app already ships. Zoom has AI Companion (and a personal note feature called My Notes). Microsoft Teams has Copilot with an "intelligent recap." Google Meet has "Take notes for me," powered by Google's Gemini model. You turn it on in the meeting and it produces live captions during the call plus a summary afterward.

The appeal is obvious: nothing new to install, nothing extra for participants to approve, and the transcript is generated by the same company that already holds the meeting's audio, so there is no third party in the loop. For a team that lives entirely inside one platform, this is often the right answer and costs nothing beyond the subscription tier you may already pay for.

The limits are equally clear. Built-in AI is platform-locked: Zoom's note-taker helps you in Zoom and nowhere else, so a team that meets on Zoom, Teams, and Google Meet in the same week gets three different transcript formats in three different places, with no single searchable archive across them. The good features are usually gated behind a higher-priced license tier. And because it is invisible and tied to the host's account, you often cannot get the transcript out into your own systems without manual export. That gap is narrowing in 2026: Google made the Meet REST API's smartNotes methods generally available on 2 April 2026, so a Workspace app can pull the "Take notes for me" file programmatically, and Zoom opened self-service purchasing for its Realtime Media Streams (RTMS) API in May 2026, which streams a meeting's audio, video and transcript to your server with no bot in the participant list.

One practical note on timing, because it surprises people. The live captions appear in real time, but the polished transcript and summary from a cloud recording are not instant. On Zoom's cloud-recording path, the processed transcript typically takes roughly twice the meeting's length to appear — a 30-minute call can take about an hour before its transcript is ready. If your workflow assumes the summary lands the second the call ends, test that assumption before you build on it.

Pattern 2 — The cloud meeting bot

This is the pattern most people picture when they hear "AI note-taker," and it is what Otter, Fireflies, and Fathom use by default. A piece of software — the "bot" — joins your meeting as if it were another attendee. It shows up in the participant list with a name like "Fireflies.ai Notetaker," it connects to the call's audio and video the same way a human's browser would, and it streams that audio to a cloud service that transcribes and summarizes it.

How does a bot "join" a call it was never invited to as a person? Underneath, the bot is usually a headless browser — a real web browser running on a server with no screen attached — that opens the meeting link and connects over WebRTC, the same real-time audio-and-video technology your own browser uses for video calls. To the meeting, it looks like one more guest who turned their camera off. That is why a bot can join Zoom, Teams, and Google Meet alike: it is just driving a browser into each one.

The strength of this pattern is reach and convenience. One tool covers every platform, it auto-joins from your calendar so you never forget to start it, and because the heavy work runs in the cloud, it does not matter whether you are on a powerful laptop or a cheap phone. This is why bots dominated the early market.

The weakness is the bot itself. It is visible — everyone sees "Notetaker" in the participant list, and in sensitive conversations that visible presence changes how people talk. Worse, that visibility is not the same thing as legal consent (more on that below). The result, in 2026, is what the industry now openly calls "bot fatigue": a measurable backlash where clients decline to meet with a bot in the room and enterprise IT teams start banning third-party auto-joiners outright. Privacy is now the single most-cited barrier to adoption in the category.

Figure 2. The bot and the bot-free app solve the same capture problem in opposite places: one joins the call from a server, the other listens from inside the device that is already in the call.

Pattern 3 — The bot-free desktop app

The reaction to bot fatigue created a third pattern, and it is the fastest-growing corner of the market. A bot-free tool — Granola is the best-known, alongside apps like Jamie — installs as a native application on your own computer (Mac, Windows, sometimes mobile). Instead of joining the call, it captures the audio your computer is already handling: the sound coming out of your speakers (everyone else) mixed with the sound from your microphone (you). The capture happens at the operating-system audio layer, on your machine, with nothing joining the meeting.

Because there is no participant to show, there is no "Notetaker has joined" announcement, no name in the list, and no waiting-room approval. And because it taps the device's own sound rather than a specific app's connection, it works across everything: Zoom, Teams, Google Meet, a Slack huddle, a browser-based call, even a phone on speaker next to the laptop. If sound comes out of the computer, the app can transcribe it.

The trade-offs are real and worth stating plainly, because the privacy-first marketing tends to skip them. The app has to be installed and running on each person's machine, so it captures your view of the meeting, not a server's clean feed — one tool per user, not one bot per call. Many bot-free tools deliberately do not keep the audio recording at all (Granola, for example, discards the audio after transcribing and offers no playback), which is great for privacy but means there is no recording to re-listen to later. And native apps have platform gaps: Granola added Android on 1 July 2026, but the Android app captures in-person conversations only. Video-call capture still runs through the macOS and Windows desktop apps, and phone-call capture is iOS-only.

A subtle point that buyers miss: "bot-free" is about visibility, not about consent. Recording someone without a visible bot does not make the recording legal where the law requires everyone's agreement. Bot-free removes the social friction of a bot in the room; it does not remove your legal duty to disclose and get consent. A July 2026 lawsuit against Granola, covered in the consent section below, turns on exactly this point.

Pattern 4 — The build-it infrastructure API

The first three patterns are products you buy. The fourth is for teams that need transcription to live inside a product they ship — a sales platform that shows call summaries on its own dashboard, a telehealth app that writes a visit note, a recruiting tool that captures interviews. For them, paying per seat for a separate note-taker is not the job; the job is getting transcripts into their own software.

There are two ways to do this, and they map onto the same capture choices as above.

The first is to rent the capture layer from an infrastructure provider. Recall.ai is the dominant one: it gives you a single API that sends a meeting bot (or runs a bot-free desktop recorder) into Zoom, Teams, Google Meet, Webex, and more, and hands your product back the audio, video, and transcript. You never maintain a fleet of headless browsers yourself. As of October 2026 its pay-as-you-go price is $0.50 per recording hour for both the bot API and the desktop SDK, billed per second, with the first 5 hours free, built-in transcription an extra $0.15 per hour, recordings stored free for 7 days, and the calendar API free. Smaller rivals undercut the headline rate: Skribby starts at $0.35 per hour, Vexa charges $0.30 plus $0.20 for transcription (or nothing if you self-host its open-source code), Nylas Notetaker bundles transcription at $0.70 per bot hour on its Pro plan, and the open-source Attendee is free if you run it yourself. Our meeting bot API comparison of Recall.ai, Skribby, MeetingBaaS and a custom build goes vendor by vendor; this lesson stays at the pattern level.

The second way is to build the capture yourself inside your own real-time stack — relevant when the meeting is your product, such as a conferencing or telehealth app you already run on WebRTC. Here you do not need a bot to join from outside, because your server is already in the call. You can transcribe centrally on the media server and fan the captions out to everyone (the SFU-side ASR pattern), run a LiveKit agent as a silent participant that produces the note-taker output, or even push recognition all the way into the browser. Those are separate lessons; the point here is that "build it" has two doors — rent an external capture API, or extend the pipeline you already own.

From audio to action: the stack every tool shares

Whichever pattern captures the audio, the steps after capture are the same across the whole market. Seeing them as one pipeline helps you read any product's feature list and know which stage each feature lives in.

Figure 3. The shared stack. Capture differs by pattern; the four stages after it are nearly identical across products, which is why they compete on integrations and polish rather than on raw transcription.

The flow is: capture, then ASR turns audio into raw words, then diarization attaches a speaker name to each line, then a language model writes the summary and pulls out action items, then integrations push the result into the tools your team already uses — a CRM like Salesforce or HubSpot, a docs tool like Notion, a chat tool like Slack. The accuracy of the transcript is decided entirely at the first two technical stages. Everything a vendor charges a premium for — the slick summary, the CRM sync, the conversation analytics — sits at the last two stages, which is exactly why the leaders look so similar on accuracy and so different on price.

The accuracy myth, with the numbers

Vendors advertise "99% accurate." Treat that the way you treat "up to" in any ad. Here are the grounded numbers from 2026 benchmarking.

Start with the human yardstick. On conversational telephone speech, IBM's best professional transcriber made 5.1% word errors on the Switchboard benchmark and 6.8% on the harder CallHome set (Saon et al., 2017), so even careful humans are not error-free on real calls. The standard way to measure transcription mistakes is word error rate, or WER: count the words the machine got wrong — substituted, inserted, or deleted — and divide by the number of words actually spoken. If a 100-word passage comes back with 5 wrong words, that is 5 ÷ 100 = 0.05, a 5% WER, which people loosely call "95% accurate." Lower WER is better.

On clean audio — one speaker at a time, good microphones, native-English speech — the best AI engines land around 5–8% WER, so roughly 92–95% accuracy, in reviewer testing updated October 2026. On messy real-world calls — crosstalk, background noise, strong accents, a bad phone connection — WER climbs to 15–20%, and Otter, for example, drops to about 85% accuracy in noisy rooms. The honest summary: on a good call every major tool is roughly as accurate as every other and close to a human, and on a hard call none of them matches a careful human.

Diarization — the who-said-what labelling — is harder than the words themselves and fails more often. Reviewer tests in 2026 put speaker attribution at about 85–90% for Otter with automatic labelling and 95% or more for the better performers on two-speaker calls, falling to 75–80% in fast conversations with five or more people; the biggest factor is whether speakers leave a brief pause between turns rather than talking over each other. If your use case depends on perfect speaker labels — a deposition, a multi-party negotiation — assume you will be correcting them by hand, and read our deeper lessons on WhisperX word-level timestamps and Pyannote diarization before you trust the automatic output.

Common pitfall: choosing on the accuracy number on the homepage. Because every leading tool is within a few points of every other on clean audio, the advertised accuracy figure is the least useful basis for a decision. Two things matter far more in practice: how the tool handles your audio conditions (heavy accents, a specific language, three people on one speakerphone), and which capture pattern fits your privacy and deployment needs. Pilot on your own real meetings — not the vendor's demo clip — and judge the summary and speaker labels, not the raw word count.

What these tools actually cost

Sticker prices cluster in a narrow band, and the free tiers differ more than the paid ones. The table below is a 2026 snapshot (consumer tools as published in March 2026, Recall.ai as of October 2026) of the four most-compared consumer tools plus the build-it option; verify current numbers before you commit, because this category re-prices often.

Read the table by how you pay, not just how much. The seat-based tools (Otter, Fireflies, Fathom, Granola) cost a flat amount per person per month, which is predictable and cheap for a team that meets a normal amount but gets expensive across a large org where many people barely use it. The usage-based option (Recall.ai) costs nothing when idle and scales with hours recorded, which suits a product that transcribes only when its users actually hold calls.

Here is the build-versus-buy arithmetic made concrete. Suppose you are building a sales tool and your customers collectively run 10,000 hours of recorded calls a month. On Recall.ai's infrastructure that is 10,000 × ($0.50 capture + $0.15 transcription) = 10,000 × $0.65 = $6,500 per month in capture-and-transcription cost, on top of which you add your own summary model and storage. Whether that beats paying a per-seat tool depends entirely on how many seats those 10,000 hours represent — which is the whole point of running the numbers rather than guessing. For the full cost model, see our real cost of AI in video products lesson.

The part the feature grids leave out: consent and the law

This is where a tooling decision quietly becomes a legal one, and where 2026 changed the picture. Treat the following as engineering-relevant context, not legal advice — confirm specifics with a qualified lawyer for your jurisdiction.

In the United States, recording-consent law splits by state. In 39 states plus the District of Columbia, one-party consent applies: if you are in the conversation, you may record it. In 11 states — including California, Illinois, and Pennsylvania — all-party consent applies, meaning every participant must agree before recording is lawful. Under the EU's GDPR, you need a lawful basis and clear, informed consent to capture someone's voice. The crucial point that catches teams out: a visible bot in the participant list is not, by itself, legal consent. No major jurisdiction treats "they could see the Notetaker" as the informed agreement the law requires. Bot-free capture is even quieter, which makes the disclosure duty more important, not less.

Two newer risks deserve a flag. First, biometrics: the speaker-recognition step that powers diarization builds a "voiceprint," and in 2026 legal analysis that voiceprint is increasingly treated as a protected biometric identifier under laws like Illinois's BIPA — meaning the who-said-what feature you take for granted can trigger explicit opt-in obligations. Second, litigation is live and moving. The Otter.ai suits filed from August 2025, Brewer v. Otter.ai among them, were consolidated as In re Otter.AI Privacy Litigation in the Northern District of California, and on 13 August 2026 the court let the federal Wiretap Act, California Invasion of Privacy Act and Illinois BIPA claims proceed while dismissing several others with leave to amend. Cruz v. Fireflies.AI, the Illinois BIPA suit over voiceprints filed in December 2025, was voluntarily dismissed without prejudice on 10 March 2026, so the question it raised is open rather than settled. And on 30 July 2026 the bot-free pattern got its own case: Chamberlain v. Granola (N.D. Cal.) alleges that participants were not told an AI notetaker was present because disclosure was off by default. No case has reached a final ruling as of October 2026, but together they have made enterprise legal teams cautious about every capture pattern, not only bots.

If you are building transcription into a product, design consent in from the start: disclose the AI's presence before it engages, capture agreement, and give users a real way to decline — the same disclosure discipline we cover in the EU AI Act and disclosure engineering lesson. In the EU, Article 50 of the AI Act has applied since 2 August 2026: an AI assistant that talks or chats with participants must make clear it is an AI, and an emotion-recognition or sentiment layer on top of the transcript must be disclosed to the people it analyses. That makes disclosure a product requirement, not a nicety.

How to choose — a short decision path

Strip away the feature lists and the choice comes down to a handful of questions in order.

Figure 4. The decision path. Four questions route you to one of the four patterns; the legal check applies to all of them.

Does transcription need to live inside software you ship? If yes, you are building, and the choice is between renting a capture API like Recall.ai and extending a real-time pipeline you already own. If no, you are buying — and then: do all your meetings happen on one platform? If yes, the platform's own AI is the cheapest, simplest answer. If you meet across several platforms, then ask whether the setting is privacy-sensitive or your clients dislike bots: if so, a bot-free desktop app keeps you invisible; if not, a cloud bot gives you the widest reach and the richest integrations. Whatever the path, run the consent check for the states and countries you operate in before you turn anything on.

Frequently asked questions

What is AI meeting transcription?

AI meeting transcription is software that captures a meeting's audio, converts it to text with automatic speech recognition, labels who said each line, and has a language model write a summary and action items. The products differ mainly in how they capture the audio, not in the transcript itself.

How do I transcribe a meeting with AI?

Turn on your platform's built-in note-taker (Zoom AI Companion, Teams Copilot or Meet "Take notes for me") if all your calls happen on one platform; otherwise add a cloud bot such as Otter or Fireflies, or a bot-free desktop app such as Granola. Tell participants before you start, because a visible bot is not legal consent.

What is the best meeting transcription API?

For transcripts inside your own product, Recall.ai has the widest platform coverage at $0.50 per recording hour plus $0.15 for transcription (October 2026); Skribby, Vexa and Nylas Notetaker are the cheaper or bundled alternatives. If the meeting already runs on your own WebRTC stack, you need no bot at all: transcribe on your media server.

How accurate is AI meeting transcription?

On clean audio the leading engines reach about 5–8% word error rate, or 92–95% accuracy (2026 reviewer tests), close to the 5.1% a professional human scores on conversational phone speech. In noise or with strong accents, error rates climb to 15–20%, and speaker labels drop from 95% to 75–80% in fast multi-person calls.

Can I transcribe a meeting without a bot joining?

Yes. A bot-free desktop app such as Granola records your computer's system audio and microphone, and Zoom's RTMS API (self-service since May 2026) and the Google Meet REST API let developers get meeting media or notes without a visible participant. None of these removes your duty to disclose recording and get consent.

Is a visible notetaker bot enough for recording consent?

No. In the 11 all-party-consent US states every participant must agree, GDPR requires a lawful basis and clear notice to everyone recorded, and no major jurisdiction treats seeing "Notetaker" in the participant list as that agreement. Speaker diarization can also create voiceprints that Illinois BIPA treats as biometric data.

How much does AI meeting transcription cost?

Seat-based note-takers start around $8–15 per user per month (Otter $8.33 and Fireflies $10 billed annually, Granola $14, Fathom about $15; 2026 list prices). Building on an API is usage-based: about $0.65 per recorded hour on Recall.ai with its transcription, so 10,000 hours a month cost about $6,500 before your own summary model.

Where Fora Soft fits in

We build the video products that these transcription features live inside — conferencing platforms, telemedicine apps, e-learning tools, and OTT systems — so we meet the build-versus-buy decision from the engineering side regularly. When transcription only needs to sit beside a client's meetings, we help them pick the right pattern and integrate it. When it has to live inside the product — a telehealth visit note generated on the platform itself (the AI scribe our AI telehealth video platform development team builds into the consult), live captions fanned out to every viewer of a webinar, a sales summary rendered on a client's own dashboard — we build that on a real-time WebRTC pipeline so the capture is native to the app rather than bolted on by an outside bot, with consent and disclosure designed in from the first sprint. The patterns in this lesson are the same ones we weigh with clients when they ask whether to buy a note-taker or own the capability. When the answer is to own it, our speech-to-text development team builds the transcription and summary pipeline on Whisper or Deepgram, and our video conferencing development team wires it into the call itself.

The book

AI for Video: A Complete Guide to Intelligence in Video Products: From Real-Time Pipelines and Agents to Serving, Cost, Compliance, and Verticals

Pattern 4 in this lesson — transcription that lives inside a product you ship — is what this volume covers end to end: where ASR goes in a WebRTC pipeline, live captions and translation, agents as engineering, serving on vLLM and Triton, cost per stream-hour, and the EU AI Act and biometric duties that decide how you disclose recording. If you are pricing Recall.ai at $0.50 per hour against your own capture layer, the cost chapters give you the model to run those numbers properly. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

See our case studies

References

1. Granola — "Meeting note tool pricing: Granola vs. Fireflies vs. Fathom vs. Otter" (2026). Per-tool free-tier limits and paid pricing (Otter 300 min/mo and $8.33/user/mo Pro; Fireflies 800-min cumulative storage and $10/$19 tiers; Fathom unlimited free recording with 5 AI summaries/mo and ~$15 Premium; Granola free Basic and $14 Business), bot vs bot-free capture, language and compliance matrix. Tier 7 (vendor comparison). https://www.granola.ai/blog/meeting-note-tool-pricing-granola-vs-fireflies-fathom-otter
2. Recall.ai — "New Recall.ai Pricing for 2026: $0.50 per Hour of Meeting Recording" (updated 6 May 2026). Build-it infrastructure pricing: $0.50/recording hour for Meeting Bot API and Desktop Recording SDK, $0.15/hour built-in transcription, free Calendar API, no platform fee, 7-day free storage then $0.05/media-hour per 30 days; enterprise customers HubSpot, Calendly, BrightHire. Tier 4 (production deployer). https://www.recall.ai/blog/new-recall-ai-pricing-for-2026
3. Zoom — "AI note taker: Your AI Meeting Assistant" and Support article "Accessing meeting transcripts for Meeting Summary with AI Companion." Native-platform capture: live captions in real time, cloud-recording transcripts taking roughly twice the meeting duration, cross-platform join into Teams and Google Meet. Tier 4. https://www.zoom.com/en/products/ai-assistant/features/ai-note-taking/
4. Read AI — "9 Best AI Meeting Assistants in 2026." Market framing of independent copilots vs platform-locked built-in AI (Zoom AI Companion, Microsoft Copilot Intelligent Recap, Google Meet "take notes for me"). Tier 7. https://www.read.ai/articles/best-ai-meeting-assistants
5. Fellow — "Best AI Meeting Note Takers Without a Bot: Top 10 Bot-Free Options for 2026." Bot-free capture mechanism: native desktop app records system audio at the OS layer, no participant entry, works across any platform. Tier 7. https://fellow.ai/blog/bot-free-ai-note-takers/
6. Saon, G. et al. (IBM) — "English Conversational Telephone Speech Recognition by Humans and Machines," Interspeech 2017 / arXiv:1703.02136. Measured professional human transcription WER of 5.1% on Switchboard and 6.8% on CallHome (Hub5 2000). Tier 3 (peer-reviewed research). https://arxiv.org/abs/1703.02136
7. AI Productivity — "AI Transcription Accuracy" (published 5 February 2026, updated 5 October 2026). Best AI tools 5–8% WER on clean audio, 15–20% in noise or with strong accents; Otter ~85% in noisy rooms; diarization Otter 85–90% auto-labelled, Fireflies 95%+, 75–80% with 5+ fast speakers. Tier 7 (reviewer tests, limited methodology). https://aiproductivity.ai/blog/ai-transcription-accuracy/
8. NIST — Speech Recognition Scoring Toolkit (SCTK / sclite) and Rich Transcription Evaluation. The de-facto authoritative definition and scoring methodology for word error rate (substitutions + insertions + deletions ÷ reference words) used across the speech-recognition field. Official standards-body reference (US NIST). https://github.com/usnistgov/SCTK
9. W3C Recommendation — "WebRTC: Real-Time Communication in Browsers" (13 March 2025). The finished real-time transport a cloud meeting bot uses to join a call and receive its audio and video, identical to the platform a human browser uses. Official standard (final Recommendation). https://www.w3.org/TR/webrtc/
10. IETF RFC 6716 — "Definition of the Opus Audio Codec" (September 2012). The default WebRTC audio codec carrying each participant's microphone audio that every transcription engine ultimately decodes. Official standard (final RFC). https://www.rfc-editor.org/rfc/rfc6716
11. Regulation (EU) 2024/1689 (EU AI Act), Article 50 — Transparency obligations. The duty to inform people when they interact with or are processed by certain AI systems — the legal basis for disclosing AI transcription before it engages. Official standard (EU regulation). https://eur-lex.europa.eu/eli/reg/2024/1689/oj
12. Regulation (EU) 2016/679 (GDPR). Lawful basis and informed-consent requirements for capturing voice and other personal data — the European baseline a visible bot does not by itself satisfy. Official standard (EU regulation). https://eur-lex.europa.eu/eli/reg/2016/679/oj
13. RecordingLaw — "AI Meeting Recording Laws by State: Complete Guide (2026)" and ReedSmith Employment Law Watch — "The legality of AI-powered recording and transcription." One-party consent in 39 states + DC, all-party consent in 11 states (incl. California, Illinois, Pennsylvania); voiceprint biometric exposure; Brewer v. Otter.ai (CA, Aug 2025) and Cruz v. Fireflies.AI (IL, Dec 2025; voluntarily dismissed March 2026). Tier 7 (legal-press orientation; confirm with counsel). https://www.recordinglaw.com/us-laws/ai-meeting-recording-laws/
14. Laxis — "The State of Meeting Note-Taking 2026" and Grand View Research — "AI Meeting Assistant Market." Market sizing: AI note-taking ~$623.5M (2025) crossing ~$740M (2026); AI meeting-assistant market ~$3.47B (2025) → $21.48B (2033) at ~25.8% CAGR; privacy as the top adoption barrier. Tier 7. https://www.laxis.com/blog/state-of-meeting-note-taking-2026/
15. Recall.ai — Pricing page (checked 17 October 2026). $0.50/recording hour for Meeting Bot API and Desktop Recording SDK on Pay As You Go, first 5 hours free, per-second billing, $0.15/hour built-in transcription, 7 days free storage then $0.05/hour, free Calendar API, startup rate $0.25/hour for the first 10,000 hours. Tier 4 (vendor pricing). https://www.recall.ai/pricing
16. Nylas — Pricing page (checked 17 October 2026). Notetaker: Free 5 bot hours, Essentials $15/month with 10 hours then $0.80/hour, Pro from $49/month with 70 hours then $0.70 per bot hour; bot hour = time in a Google Meet, Teams or Zoom meeting. Tier 4 (vendor pricing). https://nylas.com/pricing/
17. API Cost Calc — "Recall.ai vs Meeting BaaS vs Vexa cost calculator" (last checked 31 August 2026 against vendor pricing pages). Vexa $0.30/hour plus $0.20/hour transcription, Apache-2.0 self-host; Meeting BaaS token packs $0.35–0.50/hour. Tier 7 (aggregator; confirm with vendors). https://apicostcalc.com/recall-ai-vs-meetingbaas-vs-vexa-cost-calculator.html
18. Attendee — open-source meeting bot API, GitHub repository (attendee-labs/attendee). Self-hostable bot API with a free hosted sign-up at app.attendee.dev. Tier 5 (open-source project). https://github.com/attendee-labs/attendee
19. Granola — "Granola for Android: AI meeting notes for mixed-device teams" (1 July 2026). Android launch; in-person capture on Android, video calls via macOS/Windows desktop, phone-call capture iOS-only; Basic $0, Business $14, Enterprise $35 per user per month. Tier 4 (vendor). https://www.granola.ai/blog/granola-for-android-ai-meeting-notes-for-mixed-device-teams
20. Google — "Google Meet REST API release notes." smartNotes get/list methods and smartNotes event subscriptions generally available on 2 April 2026; Meet Media API listed as Developer Preview since 24 February 2025. Official documentation. https://developers.google.com/meet/docs/release-notes
21. Zoom Developer Forum — "RTMS Self-Service Purchasing is Now Available" (May 2026 update). Realtime Media Streams pay-as-you-go and credit plans purchasable self-service. Tier 4 (vendor). https://devforum.zoom.us/t/rtms-self-service-purchasing-is-now-available/144524
22. UC Today — "Otter.ai Fails to Dismiss Core Privacy Claims in U.S. Court" (18 August 2026). In re Otter.AI Privacy Litigation, N.D. Cal.: 13 August 2026 order keeps Wiretap Act, CIPA and BIPA claims; CFAA, CDAFA and some other claims dismissed with leave to amend. Tier 6 (trade press); docket at CourtListener 5:25-cv-06911. https://www.uctoday.com/productivity-automation/otter-ai-fails-to-dismiss-core-privacy-claims-in-u-s-court/
23. ToolDirectory — "AI notetaker lawsuits 2026: Otter, Granola, Fireflies" (updated 20 September 2026). Cruz v. Fireflies.AI Corp., No. 3:25-cv-03399 (C.D. Ill.), filed 18 December 2025, voluntarily dismissed without prejudice 10 March 2026; status of the Otter, Fireflies and Granola cases. Tier 7 (case roundup; check dockets on CourtListener). https://tooldirectory.ai/blog/ai-notetaker-lawsuits-2026
24. PPC Land — "Granola sued for recording meetings without consent to train AI models" (1 August 2026). Chamberlain v. Granola, Inc., No. 3:26-cv-07926-EMC (N.D. Cal.), filed 30 July 2026: disclosure off by default, training on meeting data by default; ECPA, CIPA §§631/632 and other claims. Tier 6 (trade press). https://ppc.land/granola-sued-for-recording-meetings-without-consent-to-train-ai-models/
25. Goodwin — "Not Delayed, Not Deferred: EU AI Act Transparency Obligations Are Now in Force" (August 2026). Article 50 applies from 2 August 2026 (AI-interaction disclosure, emotion-recognition notice); the AI Omnibus gives only legacy generative systems until 2 December 2026 for output marking. Tier 6 (law firm). https://www.goodwinlaw.com/en/insights/publications/2026/08/alerts-technology-dpc-eu-ai-act-transparency-obligations-now-in-force