CommunicationOS

Developer platform

An agent-first SDK for messaging

Build custom clients, internal triage queues and MCP tools. Strict types, event replay and worked prompt fixtures, so an agent can scaffold a working client in about forty minutes.

5

Languages

19

Channels, one API

MIT

Licence

41 min

Median client build

1import { CommsOS } from "@commsos/sdk";23const commsos = new CommsOS({ token: process.env.COMMSOS_TOKEN });45// One stream. Nineteen networks. Same event shape for all of them.6for await (const event of commsos.stream({ channels: "all" })) {7  if (event.type !== "message.received") continue;89  const thread = await commsos.threads.get(event.thread_id);10  const summary = await thread.summarize();11  const draft = await thread.draft({ voice: "me" });1213  await thread.send(draft.text, { requireApproval: true });14}

Scaffolding a custom client

01

Generate a key

Create a scoped token in the dashboard with explicit channel access rules.

02

Install the SDK

Pull the typed package with npm, pip, go get, SwiftPM or Gradle.

03

Open the stream

Subscribe once and receive normalised inbound payloads from every network.

04

Send a message

Dispatch text, media or a voice note through the same unified endpoint.

scaffold

$ npx @commsos/scaffold-client --framework nextjs

> Validating MCP endpoint and schema definitions... done

> Generating typed client from OpenAPI 3.1 specification

> Binding streaming listeners on 19 channels... ok

Client initialised in 41.2s. 6 files written, 0 to review.

The surface

Six integration surfaces

The SDK

Native packages for TypeScript, Python, Go, Swift and Kotlin. No runtime dependencies and full type safety across every channel.

REST API

One JSON interface for sending messages, reading historical transcripts and updating contact profiles across nineteen networks.

Streaming and webhooks

Live event feeds and HTTP webhooks with replay, backoff retries and signed headers on every delivery.

MCP server

Standard Model Context Protocol endpoints, so Claude or an OpenAI tool can read the inbox, pull context and stage drafts safely.

Agent seats

An automated process gets its own credentials, with access boundaries, send approval and a full audit trail beside the humans.

Prompt pack

System prompts, evaluation fixtures and JSON schemas that let a coding model build a working client without guessing.

Event shape

Every network, one payload

A WhatsApp voice note, a Telegram supergroup message and an email arrive with the same envelope and the same event names. Transcripts and extracted commitments are already attached. The differences that remain, like media limits and send windows, are described in one capability object per channel.

2,400 requests a minute per token on REST. Streaming events are not metered.

POST /your-endpointsigned • replayable
1{2  "id": "evt_01J9WQ2K7",3  "type": "message.received",4  "created_at": "2026-08-22T09:41:07Z",5  "channel": "whatsapp",6  "thread_id": "thr_8f21c9",7  "contact": { "id": "con_4d1", "name": "Yossi Perlman", "identities": 3 },8  "message": {9    "kind": "voice",10    "duration_ms": 72400,11    "transcript": "Yes, four thousand two hundred a carat, Thursday morning.",12    "language": "nl-BE",13    "media": [{ "id": "med_92a", "bytes": 418220, "mime": "audio/ogg" }]14  },15  "extracted": {16    "commitments": [17      { "kind": "price", "value": 4200, "currency": "USD", "unit": "carat" },18      { "kind": "deadline", "value": "2026-08-27T07:00:00Z" }19    ]20  }21}

What ships in the repo

The prompt pack

TypeScript schemas, tool definitions and the evaluation fixtures the SDK is checked against before each release. A coding agent reads them instead of guessing at the shape of a message.

Stuck developers get a shared channel with the engineers who wrote the adapter, not a ticket queue.

commsos-sdk/prompts

00-context.md

01-message-model.schema.json

02-build-a-client.prompt.md

03-routing-rules.prompt.md

04-eval-fixtures/

05-mcp-tools.json

Reference clients

Working code in under an hour

Four open source clients built on the SDK. Read them, clone them, or point your agent at one and describe the workflow you actually want.

PARCEL 4402 • LIVE19 CH ONLINE
STONEGRADEUSD/CTΔ
3.42ctVVS148,200+2.1
1.08ctVS26,940-0.4
5.61ctSI1112,500+5.8
0.74ctVVS23,180+0.2
2.15ctVS121,400-1.2
F1 QUOTE • F2 HOLD • F3 SEND4 AWAITING

Floor terminal

High-density desk workspace built for quoting stones fast.

Tauri + React + Rust

44 minutes
9:41
YPYossi P.

“Kan het vrijdag verzonden worden?”

Can it ship on Friday?

hold to reply

Field agent

Mobile client built around voice replies and translation.

React Native + Expo

38 minutes
Retention 7y • legal holdverified
a41f…9c222023-05-14 11:42voice
7b09…14ef2023-05-14 11:47text
c8d2…77a12023-05-15 09:02pdf
1e5a…b3302023-05-15 09:16text

sha256 chain intact • 4 of 4 records
exported 2026-08-19 by [email protected]

Audit browser

Read-only compliance portal with hash verification.

Next.js + Tailwind

51 minutes

commsos v1.4.2 • focus view

> yossi.perlman wa voice 1:12 09:41

ariella.wolf sg parcel 4402 09:38

rough.desk tg digest 214 08:55

baunat.purch em invoice 1187 08:22

nadia.chen ig story reply 08:31

summary 3.4ct VS1 at 4,200/ct

owed certificate by email

NORMALj/k mover reply/ search

CLI inbox

Keyboard-driven terminal reader with vim bindings.

Go + Bubble Tea

22 minutes

Build times are wall-clock, measured from an empty directory to a client sending a real message, with a coding agent doing the typing.

Get a key and a sandbox tenant

Sandbox tenants come with seeded history so your client has something real to render on the first run.

No card required. Production deployment takes under an hour.

Talk to an engineer