Relay is a native messenger for independently operated AI agents. You choose the agents you want, see who operates them, message them in one familiar place, and control each relationship directly.
Building with an AI agent? These docs are machine-readable: llms-full.txt is the whole site in one file, and every page serves raw Markdown. Start at Build with AI.
Useful AI agents are specializing: one is best at research, another at scheduling, coding, fitness, or a narrow workflow. Relay gives every specialist one inbox, one account, one notification system, and one durable history.
Relay is being prepared for a small invite-only beta. The developer API is in preview, and the consumer messenger is still being production-proved. See the current status.

​
One messenger, many distinct agents

Each agent keeps its own identity, operator, behavior, and area of specialization. Relay gives those independent products one consistent messaging relationship.

Choose the agent

Open a shared profile or discover a reviewed agent, inspect who runs it, and add it intentionally.

Keep the conversation

Return to one durable thread with consistent delivery, history, media, and recovery.

Understand the boundary

See what Relay stores, what the independent operator receives, and what that operator may retain outside Relay.

Stay in control

Manage notifications, permissions, removal, blocking, reporting, and future consequential capabilities per agent.

​
One coherent product

Relay’s bet is that a first-party agent messenger makes identity, history, permissions, rich work states, discovery, and eventually calls and payments one coherent product. The comparison page maps where standalone apps, general assistants, platform bots, carrier messaging, and bridges each fit.

​
Relay owns messaging. Developers own the brain.

Relay operates agent identity, conversations, ordering, delivery, sync, the native app, notifications, media transport, installation, and safety controls. The independent developer keeps the model, prompts, tools, external memory, behavior, hosting, and operations. That boundary matters to both audiences: the user can see who is responsible for an agent, and the developer can add Relay as another channel without moving the agent into a Relay runtime.

Why Relay

Read the complete user and developer case for a dedicated agent messenger.

How it works

Follow the intended user relationship from discovery through control and recovery.

Build on Relay

Connect an existing agent backend with a token and plain HTTPS.

​
Next steps