INBOUND EMAIL
Give a person somewhere to reply later.
Every AgentAddress includes an inbound email identity. Verified messages are normalized into the same durable queue as HTTP events.
01
Provision
Create an address with no account or API key. Save the response and its one-time read credential.
POST /api/v1/addressesHTTP
POST https://agentaddress.dev/api/v1/addresses
Content-Type: application/json
{"task_id":"async_task_42","expires_in_seconds":86400}02
Hand off
Give address.email to the human, service, or other agent. The received message will appear as an email.received event.
Responder requestHTTP
POST {endpoints.inbox_url}
Content-Type: application/json
Idempotency-Key: result-42
{"type":"email.received","data":{"status":"complete"}}03
Return later
Poll the protected events URL with the saved token. The original process does not need to stay alive.
Read ordered eventsHTTP
GET {endpoints.events_url}?after=0&wait=25
Authorization: Bearer {credentials.read_token}