Give your agent communication in one paste.

This is the whole thing an agent needs: what Caspian is and how to use it. Copy it into your agent's system prompt, or point your coding agent at it and it will wire the integration itself.

# Caspian: communication for your agent

You can reach any human on any channel through Caspian, with one persistent
identity. You never build or maintain messaging infrastructure.

## Set up (once)
pip install caspian-sdk                        # SDK + caspian CLI
caspian init                                   # mint a key, write .env
caspian connect email  --name "My Agent"       # or: telegram, slack, whatsapp, sms, voice, discord
# connect is idempotent: restarts reuse the same identity.

## Send a message
POST https://api.trycaspianai.com/v1/messages
{ "to": "user@example.com", "channel": "email", "text": "Hi, it is Ava." }
# One schema for every channel. Pick the channel, or let Caspian pick by context.

## Receive
Inbound messages arrive as normalized events (webhook or SSE) and trigger you.
Reply on the same conversation; threading and identity are handled for you.

## What you get
- One identity: a number, an inbox, a handle. The same agent everywhere.
- Every channel: WhatsApp, iMessage, Slack, Telegram, Discord, email, SMS, voice, and more.
- Lifecycle handled: reconnects, retries, rate limits, deliverability. Never babysit an adapter.

Full, always-current agent guide is served at your gateway: /SKILL.md (and /llms.txt).

Prefer to read the docs first? The full, always-current version is served at your gateway as /SKILL.md and /llms.txt, so it never drifts from the API.

Communication is the next agent primitive.

Reasoning models decide what an agent says. But an agent that cannot reliably reach the people it serves is useless, and reaching them has quietly become a separate, growing engineering problem. This is the case for owning it as a layer.

Your users are not on one platform

People live across channels. They are on WhatsApp walking, Slack working, email for anything formal, iMessage with people they trust. An agent that lives on a single platform is a person who only answers phone calls. It is not that it is worse at its job, it is that it is not present where attention already is.

Cross-platform agents win the attention problem. They meet a user in the channel that fits the moment, keep the thread when the user switches, and stay reachable the way a real colleague is. The agents people actually rely on, like OpenClaw and Hermes, are precisely the ones deployed across dozens of human channels. That reach is also exactly where their engineering time goes.

The maintenance tax is real, and measurable

The two most popular open-source agents in the world each rebuilt this layer from scratch, and the receipts are public.

The pain is not send(). Sending a message is a solved, commoditized call. The pain is lifecycle and identity: session and auth desync, reconnect loops, silent connection failures, per-channel rendering regressions on every version bump, and cross-channel identity bugs. Read the top issues in any deployed agent and this is what fills them.

Zoom out and the duplication is absurd. There are over 36,000 WhatsApp bot repositories, most standing on a handful of fragile bridge libraries where session, ban, and QR-logout lifecycle alone can be nearly 19% of all issues. Every team rebuilds the same wheel, then keeps it spinning forever. And the share of an agent codebase that is communication infrastructure only climbs as you add channels. None of it makes the agent smarter.

Identity is becoming infrastructure

Humans are the same person across every channel. Agents should be too. Today an agent is treated as five disconnected things: a Slack bot here, a WhatsApp number there, an email address somewhere else, none of them the same identity. Channels are transports, not identities, and the moment you accept that, the primitive falls out: one persistent identity, one conversation that follows the person, one place the lifecycle is owned.

The unsolved third problem: fleets and coordination

A company does not run one agent. It runs a fleet, support, sales, recruiting, scheduling, internal assistants, and that number is growing fast. Each agent needs its own identity, credentials, history, permissions, and presence. And as those fleets grow, an open problem appears: how agents coordinate and communicate, with humans and with each other, across channels, with the right identity and context attached. That multi-agent communication layer does not exist yet. It is the natural extension of owning the primitive.

So we are building the layer

AI companies should compete on intelligence, not on rebuilding messaging infrastructure. Caspian is the communication layer for AI agents: integrate once, and your agents get one identity, every channel, and none of the maintenance. You build the agent. We handle how it reaches the world.

See how it works →