Docs for Agents & LLMs

Everything here is machine-readable — point your agent at it

View as Markdown

These docs are built to be read by agents as much as by humans. If you’re integrating MeetStream with Claude, Cursor, or any LLM-driven workflow, start here.

The machine-readable surface

ResourceURLWhat it’s for
llms.txt indexdocs.meetstream.ai/llms.txtThe page index agents should fetch first
Markdown twin of any pageappend .md to any docs URLClean Markdown, no HTML chrome — e.g. docs.meetstream.ai/guides/help/faq.md
OpenAPI specdocs.meetstream.ai/openapi.jsonThe full API schema for codegen and validation

Two MCP servers (use both)

  • Docs-search MCP — https://docs.meetstream.ai/_mcp/server — searches these docs. Read-only, no key needed.
  • Action MCP — https://mcp.meetstream.ai/mcp (hosted, auth via your key) or npx @meetstream/mcp (local) — actually does things: creates bots, pulls transcripts and status, sends messages into live meetings. This is the one that lets an agent debug a real bot session.

Claude Code users can install both in one step with the plugin:

$claude plugin marketplace add meetstream-ai/meetstream

Agent-friendly CLI

Every @meetstream/cli command supports --json, so agents can drive the full API from a shell without parsing prose:

$meetstream bot create "https://meet.google.com/abc-defg-hij" -t deepgram --json
$meetstream bot status <bot_id> --json
$meetstream transcript <bot_id> --wait --json

Ground rules worth telling your agent

  • Auth is Authorization: Token <key> — Token, not Bearer. The word matters.
  • create_bot requires meeting_link AND bot_name.
  • Webhook envelopes carry both event and bot_event; branch on bot_event/bot_status for terminal reasons — details in Debugging Bots.
  • An Idempotency-Key replay returns 507 with the original bot — treat as success, never retry-loop on it.
  • Media links are presigned and expire — re-fetch the endpoint, don’t cache URLs.