Relay v1

Route

• Contract, routes, fields, events: read the locked reference and the locked

  contracts/relay-v1-openapi.yaml

  first. Report hash or source drift.
• Messaging, buttons, list pickers, rich cards, carousels, forms, payments, places, threads and voice memos: read messaging.
• Chats, contacts, sharing a card, person fields and chat activity: read chats and contacts.
• Audio and video calls, call events, and Pipecat, LiveKit or avatar integrations: read calls.

• GET /v1/me

  , who can message the agent, Log in with Relay, and the hosted MCP server's tools: read agent settings.
• Searching the public agent directory: read directory.
• Webhooks, WebSocket, ACK, replay, and sync: read agent events.
• Tokens, environments, retries, errors, and the TypeScript and Python SDKs: read SDK and auth.
• CLI setup, profiles, connection, sending any message part, other resource commands, or skill installation: read CLI and skills.

Rules

• Never invent a route, field, event, package, migration, or product rule.
• Mark behavior not proven by the contract or repository as

  unknown

  .
• Prefer

  @relaymessenger/sdk

  for TypeScript and

  relaymessenger

  for Python; show cURL for HTTP examples.
• Keep Agent Tokens in trusted backend storage and use credentials from the matching environment.
• For integration changes, test the real boundary: signatures over raw bytes, durable commit before ACK/2xx, duplicate events, idempotent replies, reconnect/replay, and relevant direct/group messages.

Rating requests

{"type":"rating_request"}

rating.created

rating.updated

rating.deleted