meetstream-migrate 1.0.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,250 @@
1
+ Metadata-Version: 2.4
2
+ Name: meetstream-migrate
3
+ Version: 1.0.0
4
+ Summary: One-command migration from Recall.ai to MeetStream.ai — scans your codebase, maps APIs, transforms code.
5
+ Home-page: https://github.com/meetstream/recall-meetstream-migration-kit
6
+ Author: MeetStream
7
+ Author-email: sid@meetstream.ai
8
+ License: MIT
9
+ Keywords: meetstream,recall,migration,meeting-bot,api
10
+ Classifier: Development Status :: 4 - Beta
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: License :: OSI Approved :: MIT License
13
+ Classifier: Programming Language :: Python :: 3
14
+ Classifier: Programming Language :: Python :: 3.8
15
+ Classifier: Programming Language :: Python :: 3.9
16
+ Classifier: Programming Language :: Python :: 3.10
17
+ Classifier: Programming Language :: Python :: 3.11
18
+ Classifier: Programming Language :: Python :: 3.12
19
+ Classifier: Topic :: Software Development :: Libraries :: Python Modules
20
+ Requires-Python: >=3.8
21
+ Description-Content-Type: text/markdown
22
+ Requires-Dist: rich>=13.0.0
23
+ Requires-Dist: requests>=2.28.0
24
+ Dynamic: author
25
+ Dynamic: author-email
26
+ Dynamic: classifier
27
+ Dynamic: description
28
+ Dynamic: description-content-type
29
+ Dynamic: home-page
30
+ Dynamic: keywords
31
+ Dynamic: license
32
+ Dynamic: requires-dist
33
+ Dynamic: requires-python
34
+ Dynamic: summary
35
+
36
+ # meetstream-migrate
37
+
38
+ One-command migration from [Recall.ai](https://recall.ai) to [MeetStream.ai](https://meetstream.ai). Scans your codebase, maps every API call, shows the diff, and migrates.
39
+
40
+ ## Why migrate?
41
+
42
+ - **~40% cheaper** — significantly lower per-hour bot and transcription costs
43
+ - **Agent-first architecture** — built for AI agents joining meetings, not just recording
44
+ - **Context layers** — real-time info fetching during calls
45
+ - **Migration CLI** — scan, preview, migrate, test in minutes
46
+
47
+ ## Quick Start
48
+
49
+ ```bash
50
+ pip install meetstream-migrate
51
+ meetstream-migrate scan ./your-recall-project
52
+ ```
53
+
54
+ Or run without installing:
55
+
56
+ ```bash
57
+ pipx run meetstream-migrate scan ./your-recall-project
58
+ ```
59
+
60
+ ## Commands
61
+
62
+ ### Scan (read-only)
63
+
64
+ Finds every Recall.ai reference in your codebase. **No files are modified.**
65
+
66
+ ```bash
67
+ meetstream-migrate scan ./your-project
68
+ ```
69
+
70
+ ### Dry Run (preview changes)
71
+
72
+ Shows exactly what would change — still no writes.
73
+
74
+ ```bash
75
+ meetstream-migrate migrate ./your-project --dry-run
76
+ ```
77
+
78
+ ### Migrate
79
+
80
+ Applies all transformations. Prompts for confirmation before writing.
81
+
82
+ ```bash
83
+ meetstream-migrate migrate ./your-project --yes
84
+ ```
85
+
86
+ ### Test APIs
87
+
88
+ Verifies your MeetStream API key works and endpoints are reachable.
89
+
90
+ ```bash
91
+ meetstream-migrate test --api-key YOUR_MEETSTREAM_API_KEY
92
+ ```
93
+
94
+ ## What It Detects
95
+
96
+ The scanner finds:
97
+
98
+ - **Base URLs** — `us-east-1.recall.ai`, `api.recall.ai`
99
+ - **API endpoints** — all 14 Recall endpoints mapped to MeetStream equivalents
100
+ - **Field names** — `meeting_url`, `recording_mode`, `metadata`, `transcription_options`, etc.
101
+ - **Webhook handlers** — `joining_call`, `in_call_recording`, `done`, `fatal`, etc.
102
+ - **SDK imports** — `import recall`, `from recall import`
103
+ - **Environment variables** — `RECALL_API_KEY`
104
+
105
+ Supported file types: `.js`, `.ts`, `.jsx`, `.tsx`, `.py`, `.go`, `.rb`, `.java`, `.env`, `.yaml`, `.json`
106
+
107
+ ## Endpoint Mapping
108
+
109
+ | Recall.ai | MeetStream.ai | Notes |
110
+ |-----------|---------------|-------|
111
+ | `POST /api/v1/bot/` | `POST /api/v1/bots/create_bot` | Field names differ |
112
+ | `GET /api/v1/bot/{id}/` | `GET /api/v1/bots/{id}/detail` | |
113
+ | `POST /api/v1/bot/{id}/leave_call/` | `GET /api/v1/bots/{id}/remove_bot` | Method change |
114
+ | `DELETE /api/v1/bot/{id}/` | `DELETE /api/v1/bots/{id}/delete` | |
115
+ | `GET /api/v1/bot/` | `GET /api/v1/bots` | List all |
116
+ | `GET /bot/{id}/audio/` | `GET /bots/{id}/get_audio` | |
117
+ | `GET /bot/{id}/video/` | `GET /bots/{id}/get_video` | |
118
+ | `GET /bot/{id}/transcript/` | `GET /transcript/{transcript_id}/get_transcript` | Uses transcript_id |
119
+ | `GET /bot/{id}/participants/` | `GET /bots/{id}/get_participants` | |
120
+ | `GET /bot/{id}/chat_messages/` | `GET /bots/{id}/get_chats` | |
121
+ | `POST /bot/{id}/send_chat_message/` | `bot_message` field on create_bot | Manual review |
122
+ | `GET /bot/{id}/screenshots/` | `GET /bots/{id}/get_screenshots` | |
123
+ | `GET /bot/{id}/speaker_timeline/` | `GET /bots/{id}/get_speaker_timeline` | |
124
+ | `POST /api/v1/webhook/` | `callback_url` on create_bot | Per-bot webhooks |
125
+
126
+ ## Field Mapping
127
+
128
+ | Recall.ai | MeetStream.ai |
129
+ |-----------|---------------|
130
+ | `meeting_url` | `meeting_link` |
131
+ | `recording_mode` (string) | `video_required` (boolean) |
132
+ | `metadata` | `custom_attributes` |
133
+ | `transcription_options` | `recording_config.transcript` |
134
+ | `noone_joined_timeout` | `voice_inactivity_timeout` |
135
+ | `destination_url` | `webhook_url` |
136
+ | `output_media.websocket.url` | `socket_connection_url.websocket_url` |
137
+
138
+ ## Webhook Event Mapping
139
+
140
+ **IMPORTANT:** MeetStream uses a **two-layer event model**, not a flat event list like Recall. You must check `event` first, then `bot_status` for detail — especially for `bot.stopped` where `bot_status` tells you *why* the bot stopped (normal exit, denied, lobby timeout, or error).
141
+
142
+ The webhook payload format is:
143
+ ```json
144
+ { "event": "bot.inmeeting", "bot_id": "...", "bot_status": "InMeeting", "message": "...", "status_code": 200, "timestamp": "...", "custom_attributes": {} }
145
+ ```
146
+
147
+ ### Bot Lifecycle Events
148
+
149
+ | Recall.ai Event | MeetStream `event` | `bot_status` | Description |
150
+ |----------------|-------------------|-------------|-------------|
151
+ | `bot.joining_call` | `bot.joining` | `Joining` | Bot connecting to meeting |
152
+ | `bot.in_waiting_room` | `bot.joining` | `Joining` | Bot in waiting room |
153
+ | `bot.in_call_not_recording` | `bot.inmeeting` | `InMeeting` | Joined, not yet recording |
154
+ | `bot.recording_permission_allowed` | `bot.inmeeting` | `InMeeting` | Recording allowed |
155
+ | `bot.recording_permission_denied` | `bot.stopped` | `Denied` | Recording denied by host |
156
+ | `bot.in_call_recording` | `bot.inmeeting` | `InMeeting` | In-call, recording |
157
+ | `bot.call_ended` | `bot.stopped` | `Stopped` | Meeting ended / bot left |
158
+ | `bot.call_ended` (lobby_timeout) | `bot.stopped` | `NotAllowed` | Bot could not join (lobby timeout) |
159
+ | `bot.done` | `bot.stopped` | `Stopped` | Bot lifecycle ended |
160
+ | `bot.fatal` | `bot.stopped` | `Error` | Unexpected error |
161
+
162
+ ### Post-Call Processing Events (MeetStream)
163
+
164
+ | Recall.ai | MeetStream `event` | Description |
165
+ |-----------|-------------------|-------------|
166
+ | `bot.done` (then fetch) | `audio.processed` | Audio ready to fetch |
167
+ | `bot.done` (then fetch) | `transcription.processed` | Transcript ready to fetch |
168
+ | `bot.done` (then fetch) | `video.processed` | Video ready to fetch |
169
+ | (no equivalent) | `data_deletion` | Bot data deleted |
170
+
171
+ ### Real-Time Events
172
+
173
+ | Recall.ai Event | MeetStream | Description |
174
+ |----------------|-----------|-------------|
175
+ | `transcript.data` | `live_transcription_required` webhook | Transcript utterance |
176
+ | `transcript.partial_data` | `live_transcription_required` webhook | Partial transcript |
177
+ | `transcript.done` | `transcription.processed` | Full transcript ready |
178
+ | `participant_events.join` | Realtime endpoint | Participant joined |
179
+ | `participant_events.leave` | Realtime endpoint | Participant left |
180
+
181
+ ### bot_status Reference
182
+
183
+ | `bot_status` | `event` | Meaning |
184
+ |-------------|---------|---------|
185
+ | `Joining` | `bot.joining` | Bot is connecting |
186
+ | `InMeeting` | `bot.inmeeting` | Bot is in the meeting and recording |
187
+ | `Stopped` | `bot.stopped` | Bot exited normally (meeting ended, removed via API, everyone left, voice timeout, etc.) |
188
+ | `NotAllowed` | `bot.stopped` | Bot could not join (commonly waiting room / lobby timeout) |
189
+ | `Denied` | `bot.stopped` | Host explicitly denied join or recording permission |
190
+ | `Error` | `bot.stopped` | Unexpected error during lifecycle |
191
+
192
+ ## Breaking Changes to Watch
193
+
194
+ These are flagged during migration and require manual review:
195
+
196
+ 1. **Transcript retrieval** — MeetStream uses `transcript_id` (returned in create_bot response), not `bot_id`
197
+ 2. **Recording mode** — Recall uses strings (`speaker_view`, `gallery_view`, `audio_only`), MeetStream uses a boolean `video_required`
198
+ 3. **Chat messages** — Recall has a separate `POST /send_chat_message/` endpoint, MeetStream uses the `bot_message` field on `create_bot`
199
+ 4. **Webhooks** — Recall registers webhooks globally via `POST /webhook/`, MeetStream uses `callback_url` per bot on creation
200
+ 5. **Webhook events** — Recall uses granular string events (`bot.joining_call`, `bot.in_call_recording`), MeetStream uses 3 lifecycle events (`bot.joining`, `bot.inmeeting`, `bot.stopped`) with `bot_status` for detail
201
+ 6. **Post-call processing** — Recall signals readiness via `bot.done`, MeetStream sends separate `audio.processed`, `transcription.processed`, and `video.processed` webhooks
202
+ 7. **Live transcription** — Recall uses `real_time_transcription.destination_url`, MeetStream uses `live_transcription_required.webhook_url` on create_bot
203
+
204
+ ## Post-Migration Checklist
205
+
206
+ After running the migration:
207
+
208
+ 1. Set `MEETSTREAM_API_KEY` in your `.env` file (get one at [app.meetstream.ai](https://app.meetstream.ai))
209
+ 2. Review all warnings from the migration output
210
+ 3. Update webhook handlers to use `event` + `bot_status` instead of Recall event names
211
+ 4. Store `transcript_id` from create_bot responses for transcript retrieval
212
+ 5. Add handlers for `audio.processed`, `transcription.processed`, `video.processed` webhooks
213
+ 6. Verify `recording_mode` → `video_required` boolean logic
214
+ 7. Run `meetstream-migrate test --api-key YOUR_KEY` to verify
215
+
216
+ ## CLI Options
217
+
218
+ ```
219
+ meetstream-migrate [command] [path] [options]
220
+
221
+ Commands:
222
+ scan [path] Scan only — show what would change
223
+ migrate [path] Scan & migrate a project (default)
224
+ test Run API tests against MeetStream.ai
225
+
226
+ Options:
227
+ --yes, -y Skip confirmation prompt
228
+ --dry-run Show changes without writing files
229
+ --api-key KEY MeetStream API key (for test command)
230
+ ```
231
+
232
+ ## Also available as an npm package
233
+
234
+ ```bash
235
+ npx @meetstream/migrate scan ./your-project
236
+ ```
237
+
238
+ See [@meetstream/migrate on npm](https://www.npmjs.com/package/@meetstream/migrate).
239
+
240
+ ## Requirements
241
+
242
+ - Python >= 3.8
243
+
244
+ ## License
245
+
246
+ MIT
247
+
248
+ ---
249
+
250
+ **Need help migrating?** Reach out at [meetstream.ai](https://meetstream.ai) — we'll walk you through it.
@@ -0,0 +1,215 @@
1
+ # meetstream-migrate
2
+
3
+ One-command migration from [Recall.ai](https://recall.ai) to [MeetStream.ai](https://meetstream.ai). Scans your codebase, maps every API call, shows the diff, and migrates.
4
+
5
+ ## Why migrate?
6
+
7
+ - **~40% cheaper** — significantly lower per-hour bot and transcription costs
8
+ - **Agent-first architecture** — built for AI agents joining meetings, not just recording
9
+ - **Context layers** — real-time info fetching during calls
10
+ - **Migration CLI** — scan, preview, migrate, test in minutes
11
+
12
+ ## Quick Start
13
+
14
+ ```bash
15
+ pip install meetstream-migrate
16
+ meetstream-migrate scan ./your-recall-project
17
+ ```
18
+
19
+ Or run without installing:
20
+
21
+ ```bash
22
+ pipx run meetstream-migrate scan ./your-recall-project
23
+ ```
24
+
25
+ ## Commands
26
+
27
+ ### Scan (read-only)
28
+
29
+ Finds every Recall.ai reference in your codebase. **No files are modified.**
30
+
31
+ ```bash
32
+ meetstream-migrate scan ./your-project
33
+ ```
34
+
35
+ ### Dry Run (preview changes)
36
+
37
+ Shows exactly what would change — still no writes.
38
+
39
+ ```bash
40
+ meetstream-migrate migrate ./your-project --dry-run
41
+ ```
42
+
43
+ ### Migrate
44
+
45
+ Applies all transformations. Prompts for confirmation before writing.
46
+
47
+ ```bash
48
+ meetstream-migrate migrate ./your-project --yes
49
+ ```
50
+
51
+ ### Test APIs
52
+
53
+ Verifies your MeetStream API key works and endpoints are reachable.
54
+
55
+ ```bash
56
+ meetstream-migrate test --api-key YOUR_MEETSTREAM_API_KEY
57
+ ```
58
+
59
+ ## What It Detects
60
+
61
+ The scanner finds:
62
+
63
+ - **Base URLs** — `us-east-1.recall.ai`, `api.recall.ai`
64
+ - **API endpoints** — all 14 Recall endpoints mapped to MeetStream equivalents
65
+ - **Field names** — `meeting_url`, `recording_mode`, `metadata`, `transcription_options`, etc.
66
+ - **Webhook handlers** — `joining_call`, `in_call_recording`, `done`, `fatal`, etc.
67
+ - **SDK imports** — `import recall`, `from recall import`
68
+ - **Environment variables** — `RECALL_API_KEY`
69
+
70
+ Supported file types: `.js`, `.ts`, `.jsx`, `.tsx`, `.py`, `.go`, `.rb`, `.java`, `.env`, `.yaml`, `.json`
71
+
72
+ ## Endpoint Mapping
73
+
74
+ | Recall.ai | MeetStream.ai | Notes |
75
+ |-----------|---------------|-------|
76
+ | `POST /api/v1/bot/` | `POST /api/v1/bots/create_bot` | Field names differ |
77
+ | `GET /api/v1/bot/{id}/` | `GET /api/v1/bots/{id}/detail` | |
78
+ | `POST /api/v1/bot/{id}/leave_call/` | `GET /api/v1/bots/{id}/remove_bot` | Method change |
79
+ | `DELETE /api/v1/bot/{id}/` | `DELETE /api/v1/bots/{id}/delete` | |
80
+ | `GET /api/v1/bot/` | `GET /api/v1/bots` | List all |
81
+ | `GET /bot/{id}/audio/` | `GET /bots/{id}/get_audio` | |
82
+ | `GET /bot/{id}/video/` | `GET /bots/{id}/get_video` | |
83
+ | `GET /bot/{id}/transcript/` | `GET /transcript/{transcript_id}/get_transcript` | Uses transcript_id |
84
+ | `GET /bot/{id}/participants/` | `GET /bots/{id}/get_participants` | |
85
+ | `GET /bot/{id}/chat_messages/` | `GET /bots/{id}/get_chats` | |
86
+ | `POST /bot/{id}/send_chat_message/` | `bot_message` field on create_bot | Manual review |
87
+ | `GET /bot/{id}/screenshots/` | `GET /bots/{id}/get_screenshots` | |
88
+ | `GET /bot/{id}/speaker_timeline/` | `GET /bots/{id}/get_speaker_timeline` | |
89
+ | `POST /api/v1/webhook/` | `callback_url` on create_bot | Per-bot webhooks |
90
+
91
+ ## Field Mapping
92
+
93
+ | Recall.ai | MeetStream.ai |
94
+ |-----------|---------------|
95
+ | `meeting_url` | `meeting_link` |
96
+ | `recording_mode` (string) | `video_required` (boolean) |
97
+ | `metadata` | `custom_attributes` |
98
+ | `transcription_options` | `recording_config.transcript` |
99
+ | `noone_joined_timeout` | `voice_inactivity_timeout` |
100
+ | `destination_url` | `webhook_url` |
101
+ | `output_media.websocket.url` | `socket_connection_url.websocket_url` |
102
+
103
+ ## Webhook Event Mapping
104
+
105
+ **IMPORTANT:** MeetStream uses a **two-layer event model**, not a flat event list like Recall. You must check `event` first, then `bot_status` for detail — especially for `bot.stopped` where `bot_status` tells you *why* the bot stopped (normal exit, denied, lobby timeout, or error).
106
+
107
+ The webhook payload format is:
108
+ ```json
109
+ { "event": "bot.inmeeting", "bot_id": "...", "bot_status": "InMeeting", "message": "...", "status_code": 200, "timestamp": "...", "custom_attributes": {} }
110
+ ```
111
+
112
+ ### Bot Lifecycle Events
113
+
114
+ | Recall.ai Event | MeetStream `event` | `bot_status` | Description |
115
+ |----------------|-------------------|-------------|-------------|
116
+ | `bot.joining_call` | `bot.joining` | `Joining` | Bot connecting to meeting |
117
+ | `bot.in_waiting_room` | `bot.joining` | `Joining` | Bot in waiting room |
118
+ | `bot.in_call_not_recording` | `bot.inmeeting` | `InMeeting` | Joined, not yet recording |
119
+ | `bot.recording_permission_allowed` | `bot.inmeeting` | `InMeeting` | Recording allowed |
120
+ | `bot.recording_permission_denied` | `bot.stopped` | `Denied` | Recording denied by host |
121
+ | `bot.in_call_recording` | `bot.inmeeting` | `InMeeting` | In-call, recording |
122
+ | `bot.call_ended` | `bot.stopped` | `Stopped` | Meeting ended / bot left |
123
+ | `bot.call_ended` (lobby_timeout) | `bot.stopped` | `NotAllowed` | Bot could not join (lobby timeout) |
124
+ | `bot.done` | `bot.stopped` | `Stopped` | Bot lifecycle ended |
125
+ | `bot.fatal` | `bot.stopped` | `Error` | Unexpected error |
126
+
127
+ ### Post-Call Processing Events (MeetStream)
128
+
129
+ | Recall.ai | MeetStream `event` | Description |
130
+ |-----------|-------------------|-------------|
131
+ | `bot.done` (then fetch) | `audio.processed` | Audio ready to fetch |
132
+ | `bot.done` (then fetch) | `transcription.processed` | Transcript ready to fetch |
133
+ | `bot.done` (then fetch) | `video.processed` | Video ready to fetch |
134
+ | (no equivalent) | `data_deletion` | Bot data deleted |
135
+
136
+ ### Real-Time Events
137
+
138
+ | Recall.ai Event | MeetStream | Description |
139
+ |----------------|-----------|-------------|
140
+ | `transcript.data` | `live_transcription_required` webhook | Transcript utterance |
141
+ | `transcript.partial_data` | `live_transcription_required` webhook | Partial transcript |
142
+ | `transcript.done` | `transcription.processed` | Full transcript ready |
143
+ | `participant_events.join` | Realtime endpoint | Participant joined |
144
+ | `participant_events.leave` | Realtime endpoint | Participant left |
145
+
146
+ ### bot_status Reference
147
+
148
+ | `bot_status` | `event` | Meaning |
149
+ |-------------|---------|---------|
150
+ | `Joining` | `bot.joining` | Bot is connecting |
151
+ | `InMeeting` | `bot.inmeeting` | Bot is in the meeting and recording |
152
+ | `Stopped` | `bot.stopped` | Bot exited normally (meeting ended, removed via API, everyone left, voice timeout, etc.) |
153
+ | `NotAllowed` | `bot.stopped` | Bot could not join (commonly waiting room / lobby timeout) |
154
+ | `Denied` | `bot.stopped` | Host explicitly denied join or recording permission |
155
+ | `Error` | `bot.stopped` | Unexpected error during lifecycle |
156
+
157
+ ## Breaking Changes to Watch
158
+
159
+ These are flagged during migration and require manual review:
160
+
161
+ 1. **Transcript retrieval** — MeetStream uses `transcript_id` (returned in create_bot response), not `bot_id`
162
+ 2. **Recording mode** — Recall uses strings (`speaker_view`, `gallery_view`, `audio_only`), MeetStream uses a boolean `video_required`
163
+ 3. **Chat messages** — Recall has a separate `POST /send_chat_message/` endpoint, MeetStream uses the `bot_message` field on `create_bot`
164
+ 4. **Webhooks** — Recall registers webhooks globally via `POST /webhook/`, MeetStream uses `callback_url` per bot on creation
165
+ 5. **Webhook events** — Recall uses granular string events (`bot.joining_call`, `bot.in_call_recording`), MeetStream uses 3 lifecycle events (`bot.joining`, `bot.inmeeting`, `bot.stopped`) with `bot_status` for detail
166
+ 6. **Post-call processing** — Recall signals readiness via `bot.done`, MeetStream sends separate `audio.processed`, `transcription.processed`, and `video.processed` webhooks
167
+ 7. **Live transcription** — Recall uses `real_time_transcription.destination_url`, MeetStream uses `live_transcription_required.webhook_url` on create_bot
168
+
169
+ ## Post-Migration Checklist
170
+
171
+ After running the migration:
172
+
173
+ 1. Set `MEETSTREAM_API_KEY` in your `.env` file (get one at [app.meetstream.ai](https://app.meetstream.ai))
174
+ 2. Review all warnings from the migration output
175
+ 3. Update webhook handlers to use `event` + `bot_status` instead of Recall event names
176
+ 4. Store `transcript_id` from create_bot responses for transcript retrieval
177
+ 5. Add handlers for `audio.processed`, `transcription.processed`, `video.processed` webhooks
178
+ 6. Verify `recording_mode` → `video_required` boolean logic
179
+ 7. Run `meetstream-migrate test --api-key YOUR_KEY` to verify
180
+
181
+ ## CLI Options
182
+
183
+ ```
184
+ meetstream-migrate [command] [path] [options]
185
+
186
+ Commands:
187
+ scan [path] Scan only — show what would change
188
+ migrate [path] Scan & migrate a project (default)
189
+ test Run API tests against MeetStream.ai
190
+
191
+ Options:
192
+ --yes, -y Skip confirmation prompt
193
+ --dry-run Show changes without writing files
194
+ --api-key KEY MeetStream API key (for test command)
195
+ ```
196
+
197
+ ## Also available as an npm package
198
+
199
+ ```bash
200
+ npx @meetstream/migrate scan ./your-project
201
+ ```
202
+
203
+ See [@meetstream/migrate on npm](https://www.npmjs.com/package/@meetstream/migrate).
204
+
205
+ ## Requirements
206
+
207
+ - Python >= 3.8
208
+
209
+ ## License
210
+
211
+ MIT
212
+
213
+ ---
214
+
215
+ **Need help migrating?** Reach out at [meetstream.ai](https://meetstream.ai) — we'll walk you through it.
@@ -0,0 +1,2 @@
1
+ """MeetStream Migration SDK — Recall.ai → MeetStream.ai"""
2
+ __version__ = "1.0.0"