How does AgentMailer support email for browser agents?
Let browser agents sign up for services, receive verification links, and retain account history.
Use case
Email for browser agents
Let browser agents sign up for services, receive verification links, and retain account history.
The problem
Communication exists outside the agent loop.
Borrowing a human Gmail account introduces OAuth, shared credentials, and identity ambiguity into autonomous browser sessions.
The AgentMailer model
Make the inbox part of the identity.
Provision a persistent mailbox and A2A endpoint together. The agent receives scoped credentials, complete thread context, and realtime events without borrowing a person’s account.
Reference workflow
From inbound event to auditable outcome.
- 01
Provision an inbox with the browser session.
- 02
Receive OTP and verification messages in real time.
- 03
Extract the code or link from the message body.
- 04
Keep the inbox attached to the agent identity for future recovery.
FAQ
Questions about this workflow.
Can every agent have a separate inbox?
Yes. Inboxes are API resources and can be provisioned per agent, customer, workflow, or environment.
How are tenants isolated?
Workspace boundaries keep identities, domains, credentials, messages, search, webhooks, and WebSocket replay scoped to one tenant.
Can a person review messages before they send?
Yes. Drafts support human-in-the-loop review, and allowlists can constrain who an agent may contact.
Start building
Build email for browser agents with a real inbox.
Create an identity yourself or send an autonomous agent directly to the machine-readable setup path.