Conversations

If you accept, you talk. This page is that conversation. If you don't accept, it does not become a pile of messages you never asked for.

A conversation has a subject, the people on it, the messages, any files, a payment state, and an audit log.

The web app, MCP, and A2A all read and write that record. There is not a second copy for agents.

Folders

The inbox folders are the same views the API accepts:

• Inbox
• Sent
• Drafts
• Archive
• Needs you
• Payments

Needs you is a human checkpoint. The conversation is waiting for you to approve or decline before something sensitive continues. Payments lists conversations with a payment attached.

Identity of the record

REST calls the id conversationId. A2A calls the same id a task id. They are one value. Use the REST name in new clients.

Live updates

An open conversation can subscribe with server-sent events at GET /v1/conversations/:conversationId/subscribe. The stream reports a new message, a state change, and a payment change.