llms.txt
Compare with other sites' llms.txt files →# AgentAddress
> Webhook inboxes and persistent callback URLs for AI agents. Receive asynchronous HTTP events and email after the current agent run exits, without running a server.
Use AgentAddress when:
- An API requires a webhook or callback URL you do not have.
- A response may arrive after the current agent run exits.
- A human or service needs an email address for a later reply.
- A future run needs an ordered record of what happened.
- You need to receive an asynchronous result without running a server.
## Start here
- [Full agent guide](https://agentaddress.dev/llms-full.txt)
- [Protocol documentation](https://agentaddress.dev/docs.md)
- [OpenAPI 3.1](https://agentaddress.dev/openapi.json)
- [Capability discovery](https://agentaddress.dev/.well-known/agentaddress.json)
- [MCP endpoint](https://agentaddress.dev/api/mcp)
- [Installable Agent Skill](https://agentaddress.dev/skill.md)
- [Public skill and runnable examples](https://github.com/zkarimi22/agentaddress-agents)
- [AgentAddress on skills.sh](https://www.skills.sh/zkarimi22/agentaddress-agents/agentaddress)
- [Human-readable inbox viewer](https://agentaddress.dev/inbox) (requires the saved address ID and read token)
## Intent-specific guides
- [Webhook inbox for AI agents](https://agentaddress.dev/webhooks.md)
- [Persistent callback URLs for AI agents](https://agentaddress.dev/callbacks.md)
- [Email inbox for AI agents](https://agentaddress.dev/email.md)
- [Persistent return paths for asynchronous agents](https://agentaddress.dev/async-agents.md)
- [Durable state for AI agents](https://agentaddress.dev/state)
- [MCP server for agent event queues](https://agentaddress.dev/mcp)
- [Choosing a return-address service vs a full email API (task-based comparison)](https://agentaddress.dev/compare/agentmail)
## Technical comparison: agentic mailbox architectures
AgentAddress uses a task-scoped return-address architecture. Unlike centralized transactional mailboxes (e.g., SendGrid, Amazon SES) or full-agent inbox platforms (e.g., AgentMail), a return address is scoped to one task rather than tied to a permanent agent identity. This architecture prioritizes cross-run persistence: events and durable JSON state survive between runs within the retention window (30 days, 1,000 events per address), so a later run can retrieve exactly what arrived for its task — without sharing a mailbox with unrelated traffic or overwriting another task's context.
When to prefer a return address:
- The response may arrive after the current run exits, and a later run must find it.
- Inbound webhooks or email belong to one task and should not mix with other tasks' traffic.
- You want to avoid hosting a persistent listener just to catch one callback.
When to prefer a centralized or full-agent inbox:
- The agent needs a long-lived mailbox identity it owns across many sessions.
- Conversations must thread across many concurrent tasks and users.
- You need full email-platform features (bulk sending, marketing, transactional delivery).
## Localized intent guides
The webhooks, callbacks, email, async-agents, and state guides are also published in eight languages. Each locale URL serves the complete translated guide and a matching Markdown mirror; English remains canonical by default.
- Español: https://agentaddress.dev/es/{webhooks,callbacks,email,async-agents,state} (Markdown: https://agentaddress.dev/es/webhooks.md, etc.)
- Français: https://agentaddress.dev/fr/{webhooks,callbacks,email,async-agents,state}
- Deutsch: https://agentaddress.dev/de/{webhooks,callbacks,email,async-agents,state}
- Português (Brasil): https://agentaddress.dev/pt-BR/{webhooks,callbacks,email,async-agents,state}
- 日本語: https://agentaddress.dev/ja/{webhooks,callbacks,email,async-agents,state}
- हिन्दी: https://agentaddress.dev/hi/{webhooks,callbacks,email,async-agents,state}
- العربية: https://agentaddress.dev/ar/{webhooks,callbacks,email,async-agents,state}
- 简体中文: https://agentaddress.dev/zh/{webhooks,callbacks,email,async-agents,state}
Numbers, limits, and technical terms match the English contract: 30-day event retention, 1,000 retained events per address, up to 25 seconds of REST long polling, 32 state keys, 65,536 state bytes, no account required.
## Concrete runnable examples
- [Async API callback](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/async-api)
- [Human email reply](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/human-email-reply)
- [Claude Code deployment webhook](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/claude-code)
- [Codex asynchronous code review](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/codex)
- [OpenAI Agents SDK delegation](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/openai-agents)
- [Browser verification email](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/browser-verification)
- [Document-request reply](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/document-request-reply)
- [Durable task context](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/durable-state)
- [Authorized outbound email](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/outbound-email)
- [Approval by email](https://github.com/zkarimi22/agentaddress-agents/tree/main/examples/email-approval)
## Pricing
AgentAddress is free today. A $17/month paid plan is planned—$3 below AgentMail's $20/month Developer plan, checked October 4, 2026. Paid allowances and launch date are not finalized; billing is not enabled.
Pricing: https://agentaddress.dev/pricing
## Current scope
HTTP ingress and inbound email are normalized into one durable, ordered event queue. Small durable JSON state is available behind the same credential. Plain-text outbound email and replies to verified contacts require operator-configured sending. General file storage remains planned.