# Developer Resources: API Docs, OpenAPI, MCP | MeetStream > Developer resources for the MeetStream meeting bot API: OpenAPI 3.1 spec, API documentation, MCP servers, authentication, webhooks, CLI, and agent discovery endpoints. Source: https://meetstream.ai/developers ## MeetStream developer resources Everything needed to build on the MeetStream meeting bot API: the OpenAPI contract, API documentation, MCP servers, authentication, webhooks, SDKs, and the agent discovery endpoints. MeetStream is a meeting bot API. One authenticated request puts a bot into a Zoom, Google Meet, or Microsoft Teams call, where it records the meeting, streams per-participant audio and video in real time, transcribes it, and can speak back into the room. This page is the index of every developer and agent surface, each at a predictable URL. ### MeetStream API documentation The full MeetStream API documentation lives at docs.meetstream.ai , covering the bot lifecycle, transcripts, participants, calendar scheduling, and webhooks. Append .md to any docs URL for clean Markdown, or /llms.txt to any section URL for a section index. ### MeetStream OpenAPI specification The machine-readable MeetStream API contract is published as OpenAPI 3.1 at meetstream.ai/openapi.json . It describes 43 paths and 57 operations, each with a unique operationId and a description, so it can be imported directly into an LLM function-calling stack, Postman, or a generated client. ### MeetStream API authentication MeetStream authenticates with an API key sent as Authorization: Token . Keys are self-serve at app.meetstream.ai and every new account includes $5 of free credit, so a first bot can run without contacting sales. The full agent-oriented walkthrough, including error codes and revocation, is at meetstream.ai/auth.md . ### MeetStream MCP server The MeetStream MCP server exposes the product as tools for Claude, Cursor, and any other MCP client. Connect over Streamable HTTP at https://mcp.meetstream.ai/mcp , or run it locally with npx -y @meetstream/mcp . A read-only documentation MCP server is available at https://docs.meetstream.ai/_mcp/server with no key required. The server card is at /.well-known/mcp/server-card.json . ### MeetStream webhooks Webhooks fire on bot lifecycle events and when recordings and transcripts become available, so an application can react the moment a call ends instead of polling. See the webhooks integration guide and the webhook events reference . ### MeetStream CLI and SDKs Create and manage meeting bots from a terminal with the MeetStream CLI ( npm install -g @meetstream/cli ). Source for the CLI and the MCP server is on the MeetStream GitHub organisation . ### Agent discovery endpoints MeetStream publishes the standard agent-discovery surfaces so an autonomous client can find and verify these resources without scraping HTML: - /llms.txt and /llms-full.txt for the agent-oriented site index - /agents.md , /developers.md and /pricing.md as plain Markdown - /.well-known/ai-catalog.json for Agentic Resource Discovery - /.well-known/mcp for MCP discovery and /.well-known/agent-card.json for A2A - /.well-known/api-catalog (RFC 9727) and /.well-known/oauth-protected-resource (RFC 9728) Every page on this site also has a Markdown twin: send Accept: text/markdown , or append /index.md to any path. ### Quickstart Send a bot into a meeting with a single request: ``` curl -X POST https://api.meetstream.ai/api/v1/bots/create_bot \ -H "Authorization: Token $MEETSTREAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"meeting_link": "https://meet.google.com/abc-defg-hij", "bot_name": "Notetaker"}' ``` Poll /api/v1/bots/{bot_id}/status until the bot has joined, then read the transcript once the call ends. Billing is per bot-hour, so remove bots that are no longer needed. --- Full site index for agents: https://meetstream.ai/llms.txt API contract (OpenAPI 3.1): https://meetstream.ai/openapi.json MCP discovery: https://meetstream.ai/.well-known/mcp