Minutes, not a wall of text
Summary, key points, decisions, action items (owner, due), open questions and topics — each anchored to the moment it was said, so you can jump back and listen.
CatalogLatency Roughly 20–40% of the recording's length (a 30-minute meeting takes about 8–12 minutes) Async true Rate Limit Per API key Max Input One recording per call, up to 2 GB (about 4 hours at the playground's bitrate)
cn8/meeting-notes
Send a meeting recording and get back structured minutes: a summary, key
Learn more about Meeting Notes Audio & Voiceasync (job)Instant previewaudiomeetingtranscription
- 1Record
- 2Review
- 3Notes
Try it
Join your meeting, then press record
We record your microphone and the meeting tab's audio into one stereo file. Chrome will ask you to pick the tab — choose the meeting and tick Share tab audio. Nothing leaves your browser until you ask for notes.
Let the other participants know they are being recorded.
Recording is free. Notes cost 0.02 credits per second of recording (≈ 72 credits per hour).
What you get
Minutes that say who decided what, with a link to the moment it was said.
Video chat launch and pricing
Launch fixed for the 30th; pricing stays as is; Sarah drafts the announcement.
Draft the launch announcement — Sarah (Friday) 06:52
Decision: launch on the 30th 06:12
Open: do we need a free tier? 20:10
- You are identified automatically; the others are told apart by voice
- Discard after the meeting and nothing is uploaded
- Copy as Markdown, or take the JSON from the API
Overview
Send a meeting recording and get back structured minutes: a summary, key points, decisions, action items with owners and due dates, open questions, topics with time ranges, and a time-coded transcript attributed to speakers. Record in stereo with your microphone on one channel and the meeting's playback on the other and you are identified as "you" automatically — only the other participants need to be told apart. Plain mono recordings and uploaded files work too.
Key capabilities
Who said what
Speaker-attributed transcript. Two-channel recordings identify you by construction; the other side is separated by voice. Rename speakers afterwards without re-processing.
Record straight from the browser
The playground records your microphone and the meeting tab's audio into one stereo file, keeps it on your machine, and uploads it only when you ask for notes. Nothing is stored if you discard the recording.
Any language, one call
Turkish, English and 90+ other languages, auto-detected. The notes are written in the meeting's language.
When to use it
Team and client meetings
Minutes ready before everyone has left the call; action items with owners you can paste into your tracker.
Interviews and user research
Full transcript with speakers plus a summary of what was learned and what remains open.
Lectures and training sessions
Topics with time ranges and key points for people who missed it.
Your own meeting product
Call the API from your app with your own recorder; you get the same structured JSON.
Input & output
input
Public URL of an audio or video recording (stereo mic/playback or mono), optional language and hints
JSON body
output
Structured notes + speaker-attributed, time-coded transcript
JSON
Guides & tips
Recording from the browser (what the playground does)
- Microphone (
getUserMedia) and the meeting tab's audio (getDisplayMedia({audio: true}), "share tab audio" ticked) are mixed with the Web Audio API into ONE stereo stream: left = microphone, right = tab. MediaRecorderwithaudio/webm;codecs=opusat 96 kbps: about 43 MB per hour.- The recording stays in the browser until you choose "Extract notes"; "Discard" throws it away without uploading.
- Zoom / Teams desktop apps have no tab audio. Record mono (microphone only — with a headset only your side is captured, with speakers both sides are) and send
channels: 1.
Getting the attribution right
- Stereo mic/playback: you are always "you"; the right channel is split by voice into Speaker 1, 2, …
- Pass
options.speakerswhen you know how many people were on the other side; it steadies the split. - Pass names in
options.participantsor rename afterwards in your UI — ids are stable within a result. - Cross-talk is kept on both sides; bleed of the speakers into your microphone is removed automatically.
Long meetings
- Processing takes roughly a third of the recording's length. Poll every 10–20 seconds or register a webhook to be called when the job finishes.
- For multi-hour sessions consider splitting at natural breaks; each part gets its own notes.
Privacy
- Tell participants they are being recorded; consent is your responsibility under KVKK/GDPR.
- Recordings are processed and deleted; only the job result (notes + transcript) is kept with your account, and you can delete the job.
Specs
Schema
Request body
audio_urlrequiredstringPublic http(s) URL of the recording (audio or video). Stereo: left = your microphone, right = the meeting's playback; mono is fine.
channelsinteger2 for a mic/playback stereo recording, 1 for a plain mono mix. Omit to detect from the file.
enum: 1, 2
languagestringISO 639-1 code of the meeting's language ("en", "tr", …). Omit to auto-detect.
expected_durationnumberRecording length in seconds. Optional — when omitted the gateway reads it from the file. Billing always uses the real length; this only sizes the credit hold taken at submission.
optionsobjectHints for attribution and notes.
speakersintegerNumber of OTHER participants (the playback side) if known.
participantsobjectNames for speaker ids, e.g. {"you": "Alex", "S1": "Sarah"}. Others are labelled "Speaker 1", "Speaker 2", …
contextstringAgenda, meeting name or anything that helps the minutes (a sentence or two).
Response
participantsarraySpeakers with id (you | S1 | S2 …), label, talk_seconds, talk_ratio.
title, summary, key_pointsstring / arrayThe minutes' headline, one-paragraph summary and 5–12 bullet points.
decisionsarray{text, at_ms} — what the group agreed on and when it was said.
action_itemsarray{owner, text, due, at_ms} — follow-ups; owner is a speaker label or a name used in the meeting, due is the phrase as said ("Friday"), empty when none.
open_questionsarray{text, at_ms} — raised but not resolved.
topicsarray{title, start_ms, end_ms, summary} — the meeting in contiguous chunks.
transcriptarray{speaker, start_ms, end_ms, text} — every line, in order.
recordingobjectHow the file was processed: mode stereo|mono, channels, ASR provider, merge stats.
Pricing
One price per second of recording; recording and discarding in the playground are free.
| Service | Unit | Price |
|---|---|---|
| Meeting Notes | second of recording | 0.02 credits/second |
A 30-minute meeting costs about 36 credits, an hour about 72.
The cost is reserved when you submit and settled to the real recording length when the job finishes; failed jobs are released in full.
The recording is deleted from our storage once the notes are produced.