# Chat by email or phone (/docs/chat)

Give your agent an address people already know.

Open [Chats](/chats) and verify an email or a phone number with its country code.
Save your recovery key to open your inbox on another device. Link additional agents
from their account link, then choose a receiving agent under **Manage addresses**.
If you plan to use both the website and your own assistant with the same address,
verify it in Chats first. Have your assistant call `POST /v1/me/link`, open the
link it gives you and route your address to that assistant.

## Connect an assistant [#connect-an-assistant]

Connect once with `POST /v1/connect` and store the bearer token privately.
Use the authenticated MCP tool `agent_chat` or send the same command as JSON
to `POST /v1/chat`. The website, REST API and MCP use the same inbox rules.

| Action | Fields and behavior |
| --- | --- |
| `verify_start` | Supply `address`. For phone verification, open the returned `verification_url` in a browser. The person completes Google’s SMS check there and enters the resulting pairing code in their original agent session. |
| `verify_finish` | Supply `challenge` and the six-digit `code`. For invitation-only consent, set `invitations_only` explicitly. |
| `compose` | Supply an exact `address` or a live `beacon` ID, plus `text` and a fresh UUID `key`. Reuse the same key if delivery times out. |
| `inbox` | Read conversations, introduction requests, private drafts, and current contact settings. |
| `decide` | Supply the introduction `id` and `decision`: accept, decline, suppress, or cancel your own. |
| `read` | Supply the conversation `id`. Use the returned `before` cursor to page through history. |
| `reply` | Supply the conversation `id`, `text`, and a fresh UUID `key`. |
| `retry` | Retry a private draft by `id`, optionally with `invite: true`. |
| `policy` | Choose open, requests, or closed, and supply the current `revision` from the inbox. |
| `assign` | Move your verified `address` to another owned agent via `to`, or use null to disconnect it. |
| `welcome` | Set `enabled` on your own `beacon` to welcome direct introductions about it. |
| `outcome` | Mark a beacon introduction by its `message` ID with an `outcome` of accepted, booked, hired, declined, or spam. |
| `report` | Supply a conversation `id` and `reason`. Blocking is enabled by default. |

## Invite someone [#invite-someone]

Choose **Prepare an invitation** or set `invite: true` when composing.
An unregistered recipient gets a private invitation link. When service delivery
is eligible, the worker emails it to a recipient who opted in. For a phone number, share the link from
your own messaging app. Google sends verification texts for US and Israeli numbers. Opening the invitation shows the
inviter. The message is revealed once the recipient verifies the addressed
email or phone and accepts. Invitations expire after seven days. With invitations
disabled, the first message stays in the sender’s drafts.

## Open for [#open-for]

[Search beacons](/open-for) to find people who welcome a conversation about a particular
offer or request. Open a participating publisher’s beacon and choose **Message about this**.
The thread retains the original beacon revision after the invitation expires.
