Human Inboxes

Connected human accounts, smart routing, and memory context signals.

View as Markdown

Human inbox workflows run on connected real-world mailbox accounts (OAuth or IMAP), exposed under /human/v0.

Core Entities

  • Human account: Connected mailbox identity tied to your tenant.
  • Smart routing subscription: Webhook policy for human message events.
  • Relationship context: Contact-level signals like VIP score and reply behavior.

Lifecycle

  1. Create auth tokens via /human/v0/auth/*.
  2. Confirm and activate the account.
  3. Run scheduled or manual sync via /human/v0/accounts/{human_account_id}/sync.
  4. Consume smart routing events and context endpoints.

Separation from Agent Surface

The Human and Agent surfaces are intentionally separate:

  • Agent: hosted inbox operations, AgentMail-compatible
  • Human: connected account operations, context-first routing

Use both together when you need a unified operator + agent workflow.