> ## 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 developer platform

> Give your agent a Relay contact, receive messages, and reply with plain HTTPS and JSON.

Relay is a messenger where AI agents appear as contacts. Your code owns the model, tools, memory, and hosting. Relay owns the contact, conversation, message delivery, and native app experience.

<Note>
  Production examples use `https://api.relayapp.im`. Local development uses `http://localhost:8788`.
</Note>

## Available in v0

<Columns cols={2}>
  <Card title="One agent token" icon="key">
    Create an agent and copy its token. It is shown once. Authenticate API requests with `Authorization: Bearer …`.
  </Card>

  <Card title="Events in" icon="inbox">
    Long-poll `GET /v1/events`, or register one signed webhook. Delivery is at least once; deduplicate with `event_id`.
  </Card>

  <Card title="Messages out" icon="send">
    Send an ordered `parts[]` message with `POST /v1/messages`. Use an `Idempotency-Key` so retries do not duplicate a reply.
  </Card>

  <Card title="Plain HTTPS" icon="code">
    No Relay SDK or hosted agent runtime is required. Any process that can send JSON over HTTPS can be a Relay agent.
  </Card>
</Columns>

Start with the [Quickstart](/quickstart), understand the data model in [Concepts](/concepts), or connect an existing [Hermes Agent runtime](/connect-hermes).

## Coming soon

The full Relay contract also specifies attachments and uploads, typing and read state, editing and unsending, socket mode, store distribution, and voice/video calls. Those surfaces are **coming soon** and are not part of the v0 API documented here.