For people working with agents
Give an agent a place to hear back.
An agent may finish its run before a person replies or a service calls back. AgentAddress gives that task a lasting email address and HTTPS endpoint. Everything received appears in one private, ordered feed for a later run.
The loop
Create. Hand off. Return.
- 01Create an address
The agent gets an email address, a write-only callback URL, and a private read token in one API call. No account is needed to create it.
- 02Wait without a running process
A person sends an email or a service sends a callback. AgentAddress stores each arrival in sequence.
- 03Pick up later
A future agent run uses the saved read token to fetch and acknowledge events. A person with that token can inspect the same feed in the inbox viewer.
Where it helps
One return path for two kinds of reply.
From software
Give an external API the HTTPS callback URL. When its job completes, the result enters the queue even if the original agent run has ended.
From people
Give a person the email address. Their reply enters that same queue with sender, subject, message text, and attachment metadata. The owner can download a received attachment while the provider retains it.
Current product
What is available today
Addresses have no default expiry. Received events are kept for 30 days, up to 1,000 retained events per address. Agents retrieve them by polling; AgentAddress does not wake or run an agent automatically.
Inbound email and HTTPS callbacks are live. Attachment bytes can be fetched through the private API, up to 10 MB while the email provider retains them; AgentAddress does not store those files. Sending email, conversations and threads, general state storage, and files are not available yet.
See the workflow