# Relay

> WhatsApp Cloud API for developers and AI agents. Meta-compatible REST proxy, free sandbox numbers, signed webhooks, hosted customer onboarding (Embedded Signup), a remote MCP server and a CLI. Meta conversation fees are passed through at cost.

Base URL: https://relay.tinyclaw.online
Auth: `X-API-Key: rk_...` (or `Authorization: Bearer rk_...`). Keys are full-access or read-only.

## Start here
- [Agent guide](https://relay.tinyclaw.online/AGENTS.md): how an agent should use this platform, safety rules, common flows
- [Full docs](https://relay.tinyclaw.online/docs.md): every endpoint, webhook event and error
- [MCP server](https://relay.tinyclaw.online/mcp): streamable HTTP, Bearer auth, grouped tools with `action` + `params`
- [CLI install](https://relay.tinyclaw.online/install.sh): `curl -fsSL https://relay.tinyclaw.online/install.sh | bash`
- [Plans](https://relay.tinyclaw.online/platform/v1/plans): JSON price list

## Send a message (Meta-compatible)
POST https://relay.tinyclaw.online/meta/whatsapp/v24.0/{phone_number_id}/messages
Body is exactly Meta's Cloud API body. Existing Cloud API code works by changing the base URL and auth header.

## Platform API
- GET /platform/v1/project, /usage, /plans
- GET|POST /platform/v1/whatsapp/phone_numbers, POST /whatsapp/sandbox_numbers, POST /whatsapp/sandbox/inbound
- GET /platform/v1/whatsapp/conversations, /conversations/{id}/messages, /messages, /contacts
- GET|POST|DELETE /platform/v1/whatsapp/templates
- GET|POST|PATCH|DELETE /platform/v1/whatsapp/webhooks, POST /webhooks/{id}/test, GET /webhook_deliveries
- GET|POST /platform/v1/whatsapp/broadcasts, /broadcasts/{id}/recipients, /broadcasts/{id}/send
- GET|POST /platform/v1/customers, POST /customers/{id}/setup_links
- GET /platform/v1/events/stream (SSE)