Skip to main content
Comms is the messaging layer for your product. You get a line on SMS and iMessage, a human inbox for handoff, and a Messages API that works like any other HTTP API you already know. Use Comms when you need to:
  • Text customers from your backend — confirmations, reminders, support, ops alerts.
  • Receive replies — poll the API or get webhooks when messages land.
  • Optionally run agents — put a no-code agent on the same line without changing how your API key works.
The key you mint is for using the line from code. It is not for controlling billing, team, or dashboard settings. The same key style, with comms_ai, calls Comms Router.

​
Choose a path

Quickstart

Mint a key, set COMMS_API_KEY, and send your first message in under a minute.

Send your first message

Walk through request body, idempotency, and how delivery works on the wire.

API reference

Base URL, auth, scopes, and every endpoint with request and response shapes.

Webhooks

Get push events when messages are sent or received instead of polling.

Connect over MCP

Point Claude, Cursor, or ChatGPT at your workspace with an API key.

Comms Router

OpenAI-shaped chat completions, billed per model.

​
How it fits together

​
What this key is not

Keep Messages API keys server-side only. Never ship them in browser code, mobile apps, or public repos.
  • Not a dashboard session or admin token.
  • Not required to use the dashboard.
  • Not scoped to “control the platform” — only to send, read, and optionally manage webhooks on the line.

​
Next steps

  1. Quickstart — create a key and land a 202.
  2. Authentication — scopes and rate limits.
  3. Send a message — full request reference.