Skip to navigation

Migrate from Recall.ai

A one-command tool that scans your Recall.ai codebase, maps every API call to its MeetStream equivalent, shows you the diff, and rewrites it, for both Node.js and Python.

View as Markdown

MeetStream covers the core Recall.ai bot workflow at a lower published price: 0.35perrecordinghour(0.35 per recording hour (0.25 at volume) versus $0.50. The migration kit does the mechanical rewrite for you and tells you exactly what, if anything, needs a human.

What it does

Point the tool at your existing Recall.ai project and it works in four passes:

  1. Scan: recursively finds Recall base URLs, endpoint calls, field names, webhook handlers, SDK imports, and RECALL_API_KEY usage.
  2. Map: prints endpoint, field, and webhook mapping tables so you can see every change before it happens.
  3. Transform: rewrites base URLs, endpoint paths, field names, webhook event handling, env vars, and imports.
  4. Report: summarizes what changed, warns on anything that needs manual review, and prints a post-migration checklist.

Run it in scan or --dry-run mode as many times as you like. Nothing is written until you confirm.

Install & run

# Scan only (no changes)
npx @meetstream/migrate scan /path/to/your-recall-project
# Dry run: see the full diff
npx @meetstream/migrate --dry-run /path/to/your-recall-project
# Migrate (asks for confirmation first)
npx @meetstream/migrate /path/to/your-recall-project
# Verify against the live API after migrating
npx @meetstream/migrate test --api-key YOUR_MEETSTREAM_API_KEY
# Full lifecycle test against a real meeting
npx @meetstream/migrate test --api-key YOUR_KEY --meeting-url https://meet.google.com/xxx-xxxx-xxx

Run the migration with a coding agent

To let Claude Code, Cursor, Codex or another coding agent run the migration, first give it the MeetStream Agent Guide. Then paste this prompt. The agent shows you the diff before it writes anything, and the acceptance criteria tell it what “done” means.

Follow the MeetStream Agent Guide.
Migrate this repository from Recall.ai to MeetStream.
Before editing, fetch https://docs.meetstream.ai/migration/migrate-from-recall.md.
Steps:
1. Run `npx @meetstream/migrate scan .` and show me the report.
2. Run `npx @meetstream/migrate --dry-run .` and summarize the diff by file.
Wait for my go-ahead before writing anything.
3. Apply the migration, then review every file it flagged by hand.
4. Check the result against the guide's hard rules. In particular: Token auth,
meeting_link, bot_name on every create, Idempotency-Key made once, and 507 as
success. Webhooks move from Recall's global endpoint to a per-bot callback_url,
and the handler branches terminals on bot_event (Agent Guide section 6).
Transcripts are fetched via transcript_id, and segment text is in `transcript`.
5. Replace RECALL_API_KEY with MEETSTREAM_API_KEY in env files and examples, never
with a real value.
6. Run `npx @meetstream/migrate test --api-key "$MEETSTREAM_API_KEY"`, then the
project's own tests.
Acceptance criteria:
- No Recall base URL, header, env var, or SDK import remains (show the grep).
- The project's test suite passes.
- One real bot runs end to end through the migrated code path, and you report
the bot_id and the events received.
- A list of anything that needs a product decision rather than a code change.

Docs: Agent Quickstarts · Webhooks and events · Errors

What gets rewritten

Endpoints

Recall.aiMeetStreamNotes
POST /api/v1/bot/POST /api/v1/bots/create_botField names differ (see below)
GET /api/v1/bot/{id}/GET /api/v1/bots/{id}/detailAlso /status
POST /api/v1/bot/{id}/leave_call/POST or GET /api/v1/bots/{id}/remove_botBoth methods work
DELETE /api/v1/bot/{id}/DELETE /api/v1/bots/{id}/delete
GET /api/v1/bot/GET /api/v1/botsList all bots
GET /bot/{id}/audio/GET /bots/{id}/get_audio
GET /bot/{id}/video/GET /bots/{id}/get_video
GET /bot/{id}/transcript/GET /transcript/{transcript_id}/get_transcriptUses transcript_id, resolved from /detail
GET /bot/{id}/participants/GET /bots/{id}/get_participants
GET /bot/{id}/chat_messages/GET /bots/{id}/get_chats
POST /bot/{id}/send_chat_message/POST /bots/{id}/send_messageBody { "message": "..." }
POST /bot/{id}/output_video/POST /bots/{id}/send_imagePublic img_url (not base64)
GET /bot/{id}/speaker_timeline/GET /bots/{id}/get_speaker_timeline
POST /api/v1/webhook/A workspace webhook endpoint in the dashboard, or callback_url on create_botWorkspace endpoints are signed; callback_url deliveries are not

Fields

Recall.aiMeetStream
meeting_urlmeeting_link
recording_modevideo_required (boolean). Defaults to false; set true to record video
recording_mode layoutrecording_config.video_layout (speaker_view or grid_view, API default grid_view)
metadatacustom_attributes
transcription_optionsrecording_config.transcript
no_one_joined_timeoutautomatic_leave.no_one_joined_timeout
assembly_aiassemblyai
destination_url (real-time transcript destination)live_transcription_required.webhook_url, with a streaming provider such as deepgram_streaming

Webhooks

Recall’s webhook becomes either a signed workspace webhook endpoint or a per-bot callback_url, and Recall’s string events map onto MeetStream’s event model:

  • Every payload carries event and bot_event. Branch on bot_event.
  • A bot’s ending arrives once, as event: "bot.stopped", with the cause in bot_event: bot.stopped, bot.kicked, bot.denied, bot.notallowed or bot.failed.
  • bot.done marks the end of post-call processing for every bot.

Before finalizing your handlers, read Webhooks and Events, or have your assistant call the webhook_events_guide tool on the MeetStream MCP server.

Capability comparison

Checked on September 24, 2026. MeetStream facts come from the product; Recall.ai facts come from Recall.ai’s public documentation and website, listed in the notes below. Only capabilities we could verify on both sides are listed.

Where MeetStream goes further

CapabilityMeetStreamRecall.ai
Recordings delivered to your own storage bucketYes: Amazon S3 (IAM role or access keys), Alibaba Cloud OSS and Cloudflare R2, including a write-only mode where MeetStream never reads your files backNot supported: recordings are downloaded from Recall and re-uploaded by you [1]
Published pay-as-you-go price per recording hour0.35/hr,0.35/hr, 0.25/hr at volume$0.50/hr [2]
Built-in transcription price$0.10/hr, waived when you use your own provider key$0.15/hr [2]

Available on both

CapabilityMeetStreamRecall.ai
Per-participant audioZoom, Google Meet and Microsoft Teams (guide)Zoom, Google Meet and Microsoft Teams, up to the 16 loudest speakers in real time [3]
Per-participant videoZoom, Google Meet and Microsoft Teams (guide)Zoom, Google Meet and Microsoft Teams (Teams up to 9 streams), plus Beta platforms [4]
Voice agents that speak in the meetingHosted voice agents configured with MIA, no web page to build or host, or your own agent over a WebSocketThe bot renders a web page you host and streams its audio and video into the meeting [5]
Transcription choices per botSix options: Deepgram, AssemblyAI, JigsawStack, Sarvam AI, MeetStream’s own transcription and meeting captions (providers)Recall.ai’s own transcription plus several third-party providers [6]
Calendar integrationGoogle Calendar and Outlook, several accounts per user (Google, Outlook)Google Calendar and Outlook [7]

Notes (all checked September 24, 2026)

  1. Source: Recall.ai documentation, “Storage and playback” page.
  2. Source: Recall.ai public pricing page.
  3. Source: Recall.ai documentation, separate audio per participant (real-time) page.
  4. Source: Recall.ai documentation, separate videos per participant (real-time) page.
  5. Source: Recall.ai documentation, “Output Media” page.
  6. Source: Recall.ai documentation, “Transcription” page.
  7. Source: Recall.ai documentation, “Calendar integration” page.

Plan your migration

  • Platforms: MeetStream bots join Zoom, Google Meet and Microsoft Teams.
  • Zoom breakout rooms and webinars: the bot stays in the main meeting.
  • Security and compliance: see the security and compliance answer in the FAQ.

What the migrator flags for review

The migrator flags Recall.ai calls that have no one-to-one MeetStream equivalent, most notably live video output into the meeting. On MeetStream, bots can show a still or animated image with Send Image, and MIA voice agents can speak in the meeting. Everything in the endpoint and field tables migrates automatically.

After migrating

  1. Swap RECALL_API_KEY for MEETSTREAM_API_KEY in your environment and secrets manager.
  2. Change the auth header to Authorization: Token <your-key>.
  3. Receive events through a workspace webhook endpoint (signed) or callback_url on create_bot.
  4. Run test --api-key ... (optionally with --meeting-url) to confirm the live API responds as expected.
  5. Review anything the report flagged for manual attention.

Prefer to drive MeetStream from a chat assistant instead of rewriting code by hand? The MeetStream MCP server gives Claude direct access to the same API.