@meetstream/cli 0.2.0 → 0.6.0

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.
package/CHANGELOG.md ADDED
@@ -0,0 +1,29 @@
1
+ # Changelog
2
+
3
+ All notable changes to `@meetstream/cli`.
4
+
5
+ ## 0.6.0 (2026-11-21)
6
+
7
+ Matches MeetStream API v1.10.0.
8
+
9
+ ### Added
10
+
11
+ - Agents API: `mia get`, `mia update <id> -f <file>` (`PUT`, whole blocks), `mia check <id>` (local agent bridge test, `GET /mia?check=local_agent`). `agents` is an alias of `mia`.
12
+ - `bot create --agent-config <id>` (alias of `--agent-config-id`) and `--agent-param key=value` for `agent_config_params`. A warning on stderr when `--socket-ws` or `--live-audio-ws` is sent with an agent.
13
+ - `balance`: prepaid balance from `GET /api/v1/billing/balance`. Available when the endpoint is on for the account; a `404` prints where to see the balance (https://app.meetstream.ai/billing) and exits 3.
14
+ - A failed transcript (`422`) prints `Transcript failed: <reason>` and the next step (`meetstream transcribe <bot-id>`), exits 4, and is never polled with `--wait`. With `--json`: `{"error": "transcript_failed", "reason", "transcript_status", "transcript_id"}`.
15
+ - A hint when the API refuses MeetStream's inbuilt keys (`MeetStream-managed keys are not available ...`): use your own key for that section.
16
+
17
+ ### Changed
18
+
19
+ - `mia create` tells you to attach the agent with `--agent-config` only (it no longer suggests `--socket-ws` / `--live-audio-ws`).
20
+ - `bot audio` / `bot video` help: download links are valid for 1 hour.
21
+ - README opens with the two ways to integrate, a fastest path for each, the voice agent setups with prices, and a "Latest docs" section.
22
+
23
+ ## 0.5.0 (2026-11-18)
24
+
25
+ - `bot raise-hand` / `bot lower-hand`, `bot create --zoom-use-own-app` / `--no-zoom-use-own-app` / `--storage-id`, Smallest AI providers, `bot timeline --download`, `Retry-After` on `429`, `/screenshots` and `/calendar/calendars` routes, `bot summary` removed (points to `transcript`).
26
+
27
+ ## 0.4.2 and earlier
28
+
29
+ See the git history.
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # MeetStream CLI
2
2
 
3
- **The MeetStream meeting-bot API from your terminal.** Create bots that join Zoom, Google Meet, and Microsoft Teams meetings; record, transcribe, and interact — without writing a line of code.
3
+ **The MeetStream meeting-bot API from your terminal.** Create bots that join Zoom, Google Meet, and Microsoft Teams meetings; record, transcribe, and interact - without writing a line of code.
4
4
 
5
5
  ```bash
6
6
  npm install -g @meetstream/cli # or: npx @meetstream/cli ...
@@ -10,9 +10,62 @@ meetstream bot create "https://meet.google.com/abc-defg-hij" -t deepgram
10
10
 
11
11
  ---
12
12
 
13
+ ## Two ways to integrate
14
+
15
+ 1. **Bot API: meeting bots and recording.** Send a bot to Zoom, Google Meet or Microsoft Teams, then get recordings, transcripts, participants, chat and webhooks after the call, or live data during the call. This is the default.
16
+ 2. **Agents API: voice agents in the meeting.** A voice agent (API name: MIA) rides on the bot and answers by voice, in the chat, or with tool calls. Use it when you want an agent that talks.
17
+
18
+ Guide: [Two ways to integrate](https://docs.meetstream.ai/guides/introduction/integration-paths).
19
+
20
+ **Path 1, fastest path.** Decide first: notes after the call (post-call), or something during the call (live)?
21
+
22
+ ```bash
23
+ # Post-call: bot, webhooks, then the transcript
24
+ meetstream bot create "https://meet.google.com/abc-defg-hij" -t meetstream -c https://you.example.com/webhook
25
+ meetstream transcript <bot_id> --wait
26
+
27
+ # Live: live transcript webhook, then raise the bot's hand while it is in the meeting
28
+ meetstream bot create "https://zoom.us/j/123456789" -t deepgram_streaming --live-transcript-webhook https://you.example.com/live
29
+ meetstream bot raise-hand <bot_id> # POST /api/v1/bots/{bot_id}/send_command {"command":"raise_hand"}
30
+ ```
31
+
32
+ **Path 2, fastest path.** Save an agent config, then send a bot with its id. Nothing else is needed on the bot.
33
+
34
+ ```bash
35
+ cat > agent.json <<'JSON'
36
+ {
37
+ "agent_name": "Meeting assistant",
38
+ "mode": "pipeline",
39
+ "transcriber": { "provider": "deepgram", "model": "nova-3", "key_source": "meetstream" },
40
+ "model": { "provider": "openai", "model": "gpt-4.1", "key_source": "meetstream",
41
+ "system_prompt": "You are a helpful meeting assistant. Keep answers short.",
42
+ "first_message": "Hi, I'm an AI assistant on this call." },
43
+ "voice": { "provider": "openai", "voice_id": "coral", "key_source": "meetstream" }
44
+ }
45
+ JSON
46
+ meetstream mia create -f agent.json # prints agent_config_id
47
+ meetstream bot create "https://meet.google.com/abc-defg-hij" --agent-config <agent_config_id>
48
+ ```
49
+
50
+ **Voice agent setups and pricing** (per meeting hour):
51
+
52
+ | Setup | What you do | Price |
53
+ |---|---|---|
54
+ | a. MeetStream's inbuilt keys (default) | `"key_source": "meetstream"` on each pipeline section, no `api_key`. Inbuilt keys cover OpenAI (LLM, speech and voice models) and Deepgram (speech-to-text) today. | Bot price + $0.25 agent infrastructure + the per-hour price of each model you pick (the dashboard agent editor shows the rate before the bot runs) |
55
+ | b. Your own keys | Your provider keys (OpenAI, Anthropic, Deepgram, ElevenLabs and others) under Integrations; `"key_source": "user"` or leave it out | Bot price + $0.25 agent infrastructure; your provider bills you for model usage |
56
+ | c. Your own agent | `"model": {"provider": "local_agent", "local_agent": {"url": "https://..."}}` with the [MeetStream Agent Kit](https://github.com/meetstream-ai/agent-kit); check it with `meetstream mia check <id>` | Bot price + $0.25 agent infrastructure; no model tokens charged for your agent's reasoning |
57
+
58
+ Bot price: $0.35 per recording hour ($0.25 at volume). The MeetStream transcription add-on is $0.10 per hour, waived with your own provider key. Details: [Voice agent pricing and keys](https://docs.meetstream.ai/guides/mia/pricing-and-keys).
59
+
60
+ If inbuilt keys are not on for your account yet, `mia create` fails with `MeetStream-managed keys are not available for <section>. Use your own key.` Switch that section to your own key (setup b) and run it again; do not loop.
61
+
62
+ Setup c is opt-in and needs the local agent feature on for your account. Meeting speech reaches an agent that has access to your computer and terminal (prompt injection), so keep the lowest access level (`readonly`) and the activation code on, and keep your computer, the agent and the bridge running for the whole call. Guide: [MIA screen sharing and custom agents](https://docs.meetstream.ai/guides/features/mia-screen-sharing-and-custom-agents).
63
+
64
+ ---
65
+
13
66
  ## Authentication
14
67
 
15
- Every command authenticates to `https://api.meetstream.ai/api/v1` with `Authorization: Token <your-key>`. There's no OAuth flow or separate CLI login — the API key **is** the credential.
68
+ Every command authenticates to `https://api.meetstream.ai/api/v1` with `Authorization: Token <your-key>`. There's no OAuth flow or separate CLI login - the API key **is** the credential.
16
69
 
17
70
  | Source | Precedence | Set with |
18
71
  |--------|------------|----------|
@@ -52,69 +105,127 @@ meetstream transcript <bot_id> --wait
52
105
 
53
106
  ## Full capability list
54
107
 
55
- ### `auth` — credentials
108
+ ### `auth` - credentials
56
109
  | Command | What it does |
57
110
  |---------|---------------|
58
111
  | `auth set-key <key>` | Stores the key in `~/.meetstream/config.json` |
59
112
  | `auth status` | Validates the configured key against the live API and shows account info |
60
113
 
61
- ### `bot` — lifecycle, media, interaction
114
+ ### `bot` - lifecycle, media, interaction
62
115
  | Command | What it does |
63
116
  |---------|---------------|
64
- | `bot create <meeting-link>` | Sends (or schedules with `--join-at`) a bot to the meeting. See [`bot create` options](#bot-create-options) below — transcription provider, callbacks, per-participant streams, MIA agent, live streaming, idempotency, and safe leave-timeout defaults. |
117
+ | `bot create <meeting-link>` | Sends (or schedules with `--join-at`) a bot to the meeting. See [`bot create` options](#bot-create-options) below - transcription provider, callbacks, per-participant streams, MIA agent, live streaming, idempotency, and safe leave-timeout defaults. |
65
118
  | `bot list` | Lists every bot on the account with id, status, and platform |
66
119
  | `bot status <id> [--watch]` | Current status; `--watch` polls every 5s until a terminal state (`Stopped`/`Done`/`Error`/etc.) |
67
- | `bot detail <id>` | Full session metadata — platform, timings, status timeline, `transcript_id`, `caption_file` |
68
- | `bot summary <id>` | MeetStream's built-in AI meeting summary |
69
- | `bot audio <id>` / `bot video <id>` | Presigned recording URL (audio valid 1h, video valid 10min) |
120
+ | `bot detail <id>` | Full session metadata - platform, timings, status timeline, `transcript_id`, `caption_file` |
121
+ | `bot summary <id>` | Removed: the API has no summary endpoint. The command exits 2 and points to `meetstream transcript <id>` |
122
+ | `bot audio <id>` / `bot video <id>` | Recording download link (valid 1 hour) |
70
123
  | `bot streams <id>` / `bot audio-streams <id>` | Per-participant video/audio streams (needs `--separate-video`/`--separate-audio` at creation) |
71
124
  | `bot participants <id>` | Everyone detected in the meeting |
72
125
  | `bot chats <id>` | In-meeting chat messages |
73
- | `bot screenshots <id>` | Screenshots captured during the meeting |
74
- | `bot timeline <id>` | Speaker timeline — who spoke when |
126
+ | `bot screenshots <id>` | Screenshots captured during the meeting, newest first, each with a 1h download URL |
127
+ | `bot timeline <id> [--download]` | Speaker timeline - who spoke when. A very large timeline comes back as `speaker_timeline_url` (a download link valid 1h, no key needed) with `size_bytes`; `--download` fetches the file and prints the timeline |
75
128
  | `bot send-message <id> <text...>` | Posts a chat message into the **live** meeting |
76
129
  | `bot send-image <id> <img-url> [-d seconds]` | Shows an image/GIF as the bot's video frame (public URL required) |
130
+ | `bot raise-hand <id>` / `bot lower-hand <id>` | Raises or lowers the bot's hand with the meeting's own control (Google Meet, Zoom, Teams). The bot must be in the meeting (`409` otherwise). Prints `hand_raised`, the state read back from the meeting. Safe to repeat |
77
131
  | `bot remove <id>` | Makes the bot leave the meeting now (data is kept) |
78
- | `bot delete <id> --yes` | **Permanently** deletes audio/video/transcripts — the `--yes` flag is mandatory, no accidental deletes |
132
+ | `bot delete <id> --yes` | **Permanently** deletes audio/video/transcripts - the `--yes` flag is mandatory, no accidental deletes |
79
133
 
80
134
  <a name="bot-create-options"></a>
81
135
  **`bot create` options:**
82
136
  ```
83
137
  -n, --name <name> bot display name (default "MeetStream Bot")
84
- --video record video (default: audio only)
138
+ --video record video as well as audio (default: audio only)
139
+ --video-layout <layout> with --video: speaker_view (default) or grid_view;
140
+ Google Meet and Teams also accept
141
+ speaker_view_default, grid_view_default
85
142
  -t, --transcript <provider> deepgram | assemblyai | sarvam | meetstream |
86
- jigsawstack | meeting_captions |
87
- deepgram_streaming | assemblyai_streaming
143
+ jigsawstack | smallest | meeting_captions |
144
+ deepgram_streaming | assemblyai_streaming |
145
+ smallest_streaming (smallest* need your Smallest AI
146
+ key saved in the dashboard)
88
147
  -l, --language <lang> transcription language (provider-specific format)
89
148
  -c, --callback <url> HTTPS webhook for lifecycle events
90
149
  --join-at <iso8601> schedule a future join, e.g. 2026-07-02T15:00:00Z
91
150
  --bot-message <msg> chat message posted when the bot joins
92
151
  --image-url <url> PUBLIC image URL for the bot avatar
93
- --retention-hours <n> data retention window (API default 24h)
152
+ --retention-hours <n> data retention window in hours (API default 720, i.e. 30 days)
94
153
  --separate-audio capture per-participant audio streams
95
154
  --separate-video capture per-participant video streams
96
- --zoom-obf use Zoom On-Behalf-Of
97
- --agent-config-id <id> attach a MIA conversational agent
155
+ --zoom-zak-url <url> Zoom: HTTPS endpoint returning a ZAK token (signed-in join)
156
+ --zoom-obf-url <url> Zoom: HTTPS endpoint returning an OBF token (on-behalf-of join)
157
+ --zoom-use-own-app Zoom: always join with your own Zoom app
158
+ --no-zoom-use-own-app Zoom: always join with no setup (not with ZAK/OBF)
159
+ --storage-id <id> save the recording to this storage destination of
160
+ your workspace (default: the workspace default)
161
+ --google-login-domain <domain> Google Meet: join signed in with an account from this
162
+ registered Workspace domain (see `logins google`)
163
+ --teams-login-domain <domain> Teams: join signed in with an account from this
164
+ registered Microsoft 365 domain (see `logins teams`)
165
+ --sign-in-email <email> signed-in bots: pin one registered account
166
+ (requires a login domain flag)
167
+ --no-strict-email with --sign-in-email: fall back to any free account
168
+ in the domain instead of failing (API default: strict)
169
+ --agent-config <id> attach a voice agent (Agents API); nothing else is
170
+ needed (alias: --agent-config-id)
171
+ --agent-param <key=value...> agent_config_params for {{variable}} placeholders
98
172
  --live-transcript-webhook <url> webhook URL for live transcript chunks
99
173
  --live-audio-ws <wss> WebSocket URL for live audio out
100
- --live-video-ws <wss> WebSocket URL for live video out
174
+ --live-video-ws <wss> reserved: accepted by the API, but live video
175
+ is not delivered yet
101
176
  --socket-ws <wss> two-way bot-control WebSocket (socket_connection_url)
102
177
  --attr <key=value...> custom_attributes entries (echoed back in webhooks)
103
- --idempotency-key <uuid> safe-retry key — a retry returns the original
178
+ --idempotency-key <uuid> safe-retry key - a retry returns the original
104
179
  bot (HTTP 507), never a duplicate
105
180
  --everyone-left-timeout <sec> leave after everyone else leaves (default 60)
106
181
  --waiting-room-timeout <sec> max seconds in waiting room (default 300)
107
182
  --max-recording-seconds <sec> max in-call recording seconds (default 14400)
108
183
  ```
109
184
 
110
- ### `transcript` / `transcriptions` / `transcribe` — transcription
185
+ **Zoom needs no setup.** Your API key and the meeting link are enough. With neither Zoom flag, the API chooses: no setup, or your own Zoom app when the account has saved Zoom app credentials or a connected Zoom account. `--zoom-zak-url` and `--zoom-obf-url` need your own Zoom app.
186
+
187
+ **Signed-in bots.** `--google-login-domain` / `--teams-login-domain` send the `google_meet` / `teams` block (`login_required: true` plus the domain, and `sign_in_email` / `strict_email` when you pin an account). Pass one domain flag, not both. The CLI warns on stderr (and still sends) if the meeting link host doesn't match the platform. Signed-in Teams bots show the Microsoft account's own name and picture, so `--name` / `--image-url` are not applied.
188
+
189
+ ```bash
190
+ meetstream bot create "https://teams.microsoft.com/l/meetup-join/..." --teams-login-domain bots.example.com
191
+ meetstream bot create "https://meet.google.com/abc-defg-hij" --google-login-domain example.com \
192
+ --sign-in-email notetaker@example.com --no-strict-email
193
+ ```
194
+
195
+ ### `logins` - accounts for signed-in bots
196
+ Register the domain once, then the accounts bots sign in as. Setup guides: [Teams](https://docs.meetstream.ai/guides/app-integrations/teams-signed-in-bots) · [Google](https://docs.meetstream.ai/guides/app-integrations/google-signed-in-bots).
197
+
111
198
  | Command | What it does |
112
199
  |---------|---------------|
113
- | `transcript <bot-id> [--wait] [--raw] [--json]` | Fetches the transcript, resolving `transcript_id` automatically (it's never in webhooks). `--wait` polls until ready. Default output is readable `Speaker: text` lines. |
114
- | `transcriptions <bot-id>` | Lists every transcription run for a bot — provider, status, presigned download URLs |
115
- | `transcribe <bot-id> -p <provider>` | (Re-)transcribes a bot's recorded audio, optionally with a different provider or language |
200
+ | `logins teams domains` / `logins teams domain <domain>` | List domains / show one domain with its accounts |
201
+ | `logins teams add-domain <domain> [--name <n>]` | Register a Microsoft 365 bot tenant domain (`login_mode` is always `always`) |
202
+ | `logins teams update-domain <domain> --name <n>` | Rename a domain |
203
+ | `logins teams remove-domain <domain> [--yes]` | Delete a domain **and all its accounts** (asks to confirm unless `--yes`) |
204
+ | `logins teams list --domain <d>` / `logins teams get <login-id>` | List accounts in a domain / show one account (lease status, last session result) |
205
+ | `logins teams add --domain <d> --email <e> [--password-stdin]` | Register an account. Teams runs **one bot per account at a time**: register N accounts for N concurrent bots |
206
+ | `logins teams set-password <login-id> [--password-stdin]` | Rotate the password (also reactivates an account disabled after a failed sign-in) |
207
+ | `logins teams disable\|enable <login-id>` | Take an account out of / back into rotation |
208
+ | `logins teams remove <login-id> [--yes]` | Delete an account |
209
+ | `logins google domains` / `domain` / `add-domain` / `update-domain` / `remove-domain` | Same as Teams, for Google Workspace domains (`add-domain` and `update-domain` also take `--login-mode always\|if_required`) |
210
+ | `logins google list --domain <d>` | List accounts in a domain |
211
+ | `logins google add --domain <d> --email <e> --key key.pem --cert cert.pem` | Register an account with the SSO private key + certificate from the setup guide (Google accounts use SSO, not passwords) |
212
+ | `logins google set-cert <login-id> --domain <d> --key <pem> --cert <pem>` | Replace an account's SSO key + certificate |
213
+ | `logins google disable\|enable\|remove <login-id> --domain <d>` | Same as Teams; Google needs the account's domain |
214
+
215
+ **Passwords are never CLI arguments** (they would land in shell history). The CLI reads them from `--password-stdin`, else `MEETSTREAM_LOGIN_PASSWORD`, else a hidden prompt, and never prints them. The API treats them as write-only.
216
+ ```bash
217
+ printf '%s' "$BOT_PASSWORD" | meetstream logins teams add --domain bots.example.com \
218
+ --email bot1@bots.example.com --password-stdin
219
+ ```
116
220
 
117
- ### `calendar` — Google Calendar auto-join
221
+ ### `transcript` / `transcriptions` / `transcribe` - transcription
222
+ | Command | What it does |
223
+ |---------|---------------|
224
+ | `transcript <bot-id> [--wait] [--raw] [--json]` | Fetches the transcript, resolving `transcript_id` automatically (it's never in webhooks). `--wait` polls until ready. Default output is readable `Speaker: text` lines. A failed transcript (`422`) prints `Transcript failed: <reason>` and the next step, and exits with code 4: it will not become ready, so fix the cause and run `transcribe`. |
225
+ | `transcriptions <bot-id>` | Lists every transcription run for a bot - provider, status, download links |
226
+ | `transcribe <bot-id> -p <provider>` | (Re-)transcribes a bot's recorded audio, optionally with a different provider (`deepgram`, `assemblyai`, `sarvam`, `meetstream`, `jigsawstack`, `smallest`) or language |
227
+
228
+ ### `calendar` - Google Calendar auto-join
118
229
  | Command | What it does |
119
230
  |---------|---------------|
120
231
  | `calendar connect --client-id --client-secret --refresh-token` | Connects a Google Calendar via OAuth refresh-token flow |
@@ -125,14 +236,24 @@ meetstream transcript <bot_id> --wait
125
236
  | `calendar reschedule <bot-id> <iso8601>` | Change a scheduled bot's join time |
126
237
  | `calendar cancel <bot-id>` | Delete a scheduled (not-yet-joined) bot |
127
238
 
128
- ### `mia` — conversational AI agents
239
+ ### `mia` (alias `agents`) - Agents API, voice agent configs
129
240
  | Command | What it does |
130
241
  |---------|---------------|
131
242
  | `mia list` | Lists agent configs |
132
- | `mia create -f <config.json>` | Creates an agent config (`agent_name`, `mode`, `model`, `voice`, `transcriber`, …) — attach it to a bot with `--agent-config-id` |
243
+ | `mia get <agent-config-id>` | Shows one agent config (secrets come back masked) |
244
+ | `mia create -f <config.json>` | Creates an agent config (`agent_name`, `mode`, `model`, `voice`, `transcriber`, `agent`, ...). Attach it with `bot create <link> --agent-config <id>` |
245
+ | `mia update <agent-config-id> -f <blocks.json>` | Updates a config (`PUT`): each block in the file replaces the saved block, so send whole blocks. Running bots are not changed |
133
246
  | `mia delete <agent-config-id>` | Deletes an agent config |
247
+ | `mia check <agent-config-id>` | Tests the connection to your local agent bridge (`model.provider: "local_agent"`). Exits 3 when the status is not `ok` |
248
+
249
+ The config file takes the fields of the [MIA API guide](https://docs.meetstream.ai/guides/mia/mia-api-guide), including `key_source` on `transcriber` / `model` / `voice`, `transcriber.language`, and the agent options `agent.tools` (`["screen"]` on Google Meet), `agent.chat_input`, `agent.quiet_actions` and `agent.speak_only_when_asked`.
134
250
 
135
- ### `listen` — local webhook receiver
251
+ ### `balance` - prepaid balance
252
+ | Command | What it does |
253
+ |---------|---------------|
254
+ | `balance [--json]` | Shows your prepaid balance (`GET /api/v1/billing/balance`, read only). Available when the balance endpoint is on for your account; until then it prints where to see the balance (https://app.meetstream.ai/billing) and exits 3 |
255
+
256
+ ### `listen` - local webhook receiver
136
257
  | Command | What it does |
137
258
  |---------|---------------|
138
259
  | `listen [-p port] [--path path] [--forward url] [--json]` | Runs a local HTTP server that pretty-prints every MeetStream webhook event as it arrives, color-coded by outcome. Pair with `ngrok http <port>` to give `bot create --callback` a public URL during development. `--forward` also relays the raw payload to another URL. |
@@ -141,19 +262,19 @@ Every command supports `--json` for scripting.
141
262
 
142
263
  ---
143
264
 
144
- ## The webhook model — live-verified
265
+ ## The webhook model - live-verified
145
266
 
146
- Events arrive under the **`event`** key with `bot_id`, `bot_status`, `message`, `status_code` (200/500), `custom_attributes` — this is exactly what `meetstream listen` decodes and pretty-prints for you:
267
+ Every event carries **`event`**, `bot_id`, `message`, `status_code` (200/500), `custom_attributes` and `timestamp`, and most also carry **`bot_event`**. This is exactly what `meetstream listen` decodes and pretty-prints for you:
147
268
 
148
269
  ```
149
270
  bot.joining → bot.in_waiting_room → bot.inmeeting → bot.recording → bot.leaving → bot.stopped
150
271
  → manifest.completed → audio.processed → transcription.processed → video.processed → bot.done
151
272
  ```
152
273
 
153
- - **`bot.stopped` fires once** — `bot_status` says why (`Stopped` normal · `NotAllowed` lobby-timeout · `Denied` host-denied · `Error` crash).
154
- - **Streaming-only transcription providers** (`deepgram_streaming`, `assemblyai_streaming`, `meeting_captions`) end at `audio.processed` — they never fire `transcription.processed`, `transcription.failed`, or `bot.done`.
155
- - **`transcript_id` is not in webhooks** — `meetstream transcript <bot_id>` resolves it via `/detail` automatically.
156
- - The public docs page for this describes a different (`bot_event`) envelope key — that's inaccurate; this CLI, and the [MeetStream MCP server](https://github.com/meetstream-ai/meetstream-mcp), both implement the live-verified model above.
274
+ - **Terminals are two-layer.** Every ending arrives once as `event: "bot.stopped"`, and `bot_event` says why: `bot.stopped` (normal), `bot.kicked` (removed by a participant), `bot.notallowed` (lobby timeout), `bot.denied` (host refused), `bot.failed` (crash). Not admitted, denied and failed carry `status_code: 500`. Branch on `bot_event`: a kick and a clean exit both report `bot_status: "Stopped"`.
275
+ - **Streaming-only transcription providers** (`deepgram_streaming`, `assemblyai_streaming`, `meeting_captions`) never fire `transcription.processed` or `transcription.failed`. `bot.done` still fires, on every path.
276
+ - **`transcript_id` is not in webhooks** - `meetstream transcript <bot_id>` resolves it via `/detail` automatically.
277
+ - The [MeetStream MCP server](https://github.com/meetstream-ai/meetstream-mcp)'s `webhook_events_guide` tool describes the same model.
157
278
 
158
279
  ---
159
280
 
@@ -170,9 +291,14 @@ bot.joining → bot.in_waiting_room → bot.inmeeting → bot.recording → bot.
170
291
  | Symptom | Fix |
171
292
  |---------|-----|
172
293
  | "No API key found" | Run `meetstream auth set-key <key>` or `export MEETSTREAM_API_KEY=...` |
173
- | `auth status` fails with 401 | Key is invalid/revoked — generate a new one at [app.meetstream.ai/api-keys](https://app.meetstream.ai/api-keys) |
174
- | `transcript` returns "not ready yet" | The meeting isn't fully processed, or the provider is streaming-only (no post-call transcript) — check `bot status` first |
175
- | `listen` events never arrive | Confirm the bot's `--callback` URL is a public HTTPS URL (use `ngrok http <port>`) — MeetStream will not retry non-2xx or unreachable webhooks |
294
+ | `auth status` fails with 401 | Key is invalid/revoked - generate a new one at [app.meetstream.ai/api-keys](https://app.meetstream.ai/api-keys) |
295
+ | `transcript` prints "Transcript failed: ..." (exit 4) | The transcript ended `Failed` (API `422`), for example the provider rejected the key or its usage limit was reached. Fix the cause, then `meetstream transcribe <bot-id>` |
296
+ | `mia create` fails with "MeetStream-managed keys are not available" | Inbuilt keys are not on for your account yet. Use your own provider key for that section (`"key_source": "user"`) |
297
+ | `transcript` returns "not ready yet" | The meeting isn't fully processed, or the provider is streaming-only (no post-call transcript) - check `bot status` first |
298
+ | `bot create` with a login domain fails with 400 "not registered" | Register the domain first: `meetstream logins teams add-domain <domain>` (or `logins google add-domain`) |
299
+ | Signed-in Teams bot fails with 409 / 429 | The pinned account is busy or deactivated, or every account is in use. Add accounts (`logins teams add`), rotate a password (`set-password`), or use `--no-strict-email` |
300
+ | `HTTP 429 ... (retry after N s)` on `bot create` | Prepaid accounts can create only a few bots per minute and per hour. Wait N seconds, then run the command again with the same `--idempotency-key`. With `--json`, the error has `retry_after` |
301
+ | `listen` events never arrive | Confirm the bot's `--callback` URL is a public HTTPS URL (use `ngrok http <port>`) - MeetStream will not retry non-2xx or unreachable webhooks |
176
302
 
177
303
  ## Development
178
304
 
@@ -183,7 +309,15 @@ npm test # node --test, fully mocked (no network)
183
309
 
184
310
  ---
185
311
 
186
- Docs: [docs.meetstream.ai](https://docs.meetstream.ai) · OpenAPI: [openapi.json](https://docs.meetstream.ai/openapi.json) · MCP server for AI agents: [@meetstream/mcp](https://github.com/meetstream-ai/meetstream-mcp) · Migrating from Recall.ai: [@meetstream/migrate](https://github.com/meetstream-ai/recall-meetstream-migration-kit)
312
+ ## Latest docs
313
+
314
+ - [Two ways to integrate](https://docs.meetstream.ai/guides/introduction/integration-paths) · [CLI](https://docs.meetstream.ai/build-with-ai/meetstream-cli)
315
+ - [Create Bot payload reference](https://docs.meetstream.ai/api-reference/create-bot-payload-reference) · [Webhooks and events](https://docs.meetstream.ai/guides/webhooks/webhooks-and-events) · [Errors](https://docs.meetstream.ai/errors)
316
+ - [MIA API guide](https://docs.meetstream.ai/guides/mia/mia-api-guide) · [Voice agent pricing and keys](https://docs.meetstream.ai/guides/mia/pricing-and-keys)
317
+
318
+ For the latest details, fetch the page with `.md` appended, read https://docs.meetstream.ai/llms.txt, or connect the docs MCP server at https://docs.meetstream.ai/_mcp/server. If this README and the docs differ, the docs are correct.
319
+
320
+ OpenAPI: [openapi.json](https://docs.meetstream.ai/openapi.json) · Hosted MCP server for AI agents: `https://mcp.meetstream.ai/mcp` ([docs](https://docs.meetstream.ai/build-with-ai/meetstream-mcp-server)) · Migrating from Recall.ai: [@meetstream/migrate](https://www.npmjs.com/package/@meetstream/migrate) · Changes: [CHANGELOG.md](CHANGELOG.md)
187
321
 
188
322
  MIT © MeetStream.ai
189
323
 
package/bin/meetstream.js CHANGED
@@ -1,5 +1,5 @@
1
1
  #!/usr/bin/env node
2
- // MeetStream CLI — https://github.com/meetstream-ai/meetstream-cli
2
+ // MeetStream CLI - https://github.com/meetstream-ai/meetstream-cli
3
3
  import { Command } from 'commander';
4
4
  import { createRequire } from 'node:module';
5
5
  import { MeetStreamClient } from '../src/api.js';
@@ -7,8 +7,9 @@ import { resolveApiKey } from '../src/config.js';
7
7
  import { fail } from '../src/output.js';
8
8
  import { registerBotCommands } from '../src/commands/bot.js';
9
9
  import { registerTranscriptCommands } from '../src/commands/transcript.js';
10
- import { registerAuthCommands, registerCalendarCommands, registerMiaCommands } from '../src/commands/misc.js';
10
+ import { registerAuthCommands, registerCalendarCommands, registerMiaCommands, registerBalanceCommand } from '../src/commands/misc.js';
11
11
  import { registerListenCommand } from '../src/commands/listen.js';
12
+ import { registerLoginsCommands } from '../src/commands/logins.js';
12
13
  import { track, shutdownTelemetry } from '../src/telemetry.js';
13
14
 
14
15
  const require = createRequire(import.meta.url);
@@ -17,7 +18,7 @@ const { version } = require('../package.json');
17
18
  const program = new Command();
18
19
  program
19
20
  .name('meetstream')
20
- .description('MeetStream — meeting bot API from your terminal (Zoom, Google Meet, Teams)\nDocs: https://docs.meetstream.ai · Keys: https://app.meetstream.ai/api-keys')
21
+ .description('MeetStream - meeting bot API from your terminal (Zoom, Google Meet, Teams)\nDocs: https://docs.meetstream.ai · Keys: https://app.meetstream.ai/api-keys')
21
22
  .version(version);
22
23
 
23
24
  let client;
@@ -31,6 +32,8 @@ registerBotCommands(program, getClient);
31
32
  registerTranscriptCommands(program, getClient);
32
33
  registerCalendarCommands(program, getClient);
33
34
  registerMiaCommands(program, getClient);
35
+ registerBalanceCommand(program, getClient);
36
+ registerLoginsCommands(program, getClient);
34
37
  registerListenCommand(program);
35
38
 
36
39
  program.hook('preAction', (thisCmd, actionCmd) => {
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@meetstream/cli",
3
- "version": "0.2.0",
4
- "description": "Official MeetStream CLI \u2014 create meeting bots, fetch transcripts, and stream webhook events from your terminal. Zoom, Google Meet, Microsoft Teams.",
3
+ "version": "0.6.0",
4
+ "description": "Official MeetStream CLI: create meeting bots, fetch transcripts, and stream webhook events from your terminal. Zoom, Google Meet, Microsoft Teams, including signed-in bots.",
5
5
  "type": "module",
6
6
  "bin": {
7
7
  "meetstream": "bin/meetstream.js"
@@ -10,7 +10,8 @@
10
10
  "bin",
11
11
  "src",
12
12
  "README.md",
13
- "LICENSE"
13
+ "LICENSE",
14
+ "CHANGELOG.md"
14
15
  ],
15
16
  "scripts": {
16
17
  "test": "node --test"