> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relayapp.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Relay for developers

> Add Relay as a consumer messaging channel to an agent backend you already run.

Relay gives independently hosted AI agents a native place to message users.
Relay handles agent profiles, conversations, delivery, sync, the native app,
installation, and safety controls; your backend handles the model, tools,
external memory, behavior, hosting, and operations.

The developer opportunity follows from the consumer product: people get one
trusted place for distinct agents, while each operator can reach that relationship
without shipping another complete mobile client.

<Note>
  **Building with an AI agent?** Feed these docs straight to your LLM or coding
  agent: [`llms-full.txt`](https://docs.relayapp.im/llms-full.txt) is the complete
  documentation in one file, and [`llms.txt`](https://docs.relayapp.im/llms.txt)
  is a concise index. More in [Build with AI](/ai).
</Note>

<Warning>
  The API is in developer preview. The published quickstart is proved end to end
  against production, and the consumer messenger is still being production-proved
  for multi-user use. [See the current status](/current-status).
</Warning>

## Add Relay as another channel

Keep the agent backend and channels you already run. Register one Relay webhook
and send the same handler's output back through plain HTTPS.

<Columns cols={2}>
  <Card title="Quickstart" icon="bolt" href="/quickstart">
    Register a signed webhook, receive one message, and reply with one request.
  </Card>

  <Card title="Receive messages" icon="inbox" href="/guides/webhooks">
    Receive signed HTTPS events with durable retries. `event_id` makes redelivery safe.
  </Card>

  <Card title="Send rich replies" icon="send" href="/guides/sending-messages">
    Send ordered text, media, voice memos, rich link previews, and structured data. Reply to a message or target one part of it.
  </Card>

  <Card title="Pipe native output" icon="water" href="/guides/streaming">
    Pipe a supported UI message stream in one request. Relay stores one final message.
  </Card>

  <Card title="Build with AI" icon="sparkles" href="/ai">
    Machine-readable docs, the MCP server, and a paste-ready integration brief for your coding agent.
  </Card>

  <Card title="Text your coding agent" icon="terminal" href="/guides/coding-agents">
    Bridge Claude Code, Codex, or Hermes to your phone through a Relay agent.
  </Card>

  <Card title="Vercel AI SDK" icon="triangle" href="/guides/vercel-ai-sdk">
    Verify signed webhooks and stream `streamText` output as one canonical message.
  </Card>
</Columns>

Start by [receiving and replying to one message](/quickstart), then connect the
same handler your other messaging channels already use. Read the [data model](/concepts)
when you need richer message parts.

<Note>
  **Building with a coding agent?** Give it [`llms-full.txt`](https://docs.relayapp.im/llms-full.txt), the [integration brief](/ai), or Relay's docs MCP server.
</Note>

## Current preview boundary

The current developer preview is webhooks plus the REST API. Socket mode,
agent-initiated group management, and calls ship later. See [developer preview
availability](/roadmap) for the full matrix.

## Next steps

* [Quickstart](/quickstart)
* [Create and connect an agent](/guides/your-agent)
* [Authentication](/authentication)
* [API overview](/api-reference/overview)