Scoped agent identities
Operators create readable addresses and API keys for each agent, then pause, resume, archive, or route them through catch-all rules.
← Back to Open source
02Open-source build
AgentBox
Open-source email infrastructure that gives software agents an inbox, an identity, and enforceable sending rules.
sagnik11/agentbox
02
01Amazon SES
02S3 and SNS ingest
03AgentBox control plane
04REST, SDK, or MCP
Purpose
The reason for the build
Agents need email accounts that operators can inspect and restrict. AgentBox provides the control plane while the customer keeps mail delivery inside their own AWS account.
Architecture
How the pieces connect
AgentBox provisions Amazon SES, S3, and SNS without replacing an existing receipt-rule set. It ingests raw MIME, threads messages, stores attachments, and exposes mail through REST, realtime events, SDKs, MCP tools, and an operator console.
Capabilities
What the project handles
Outbound guardrails
Allow lists, approval queues, daily limits, suppressions, and loop prevention put boundaries around autonomous sending.
Durable delivery
Idempotent ingestion, cursor-based events, signed webhooks, retries, and dead-letter replay protect mail workflows from duplicate or lost work.
Operator visibility
The console, audit log, health views, and configuration diff give a human a clear record of each agent mailbox.
Build notes
Constraints that shaped it
01
Customer AWS accounts remain the mail servers. AgentBox manages configuration and agent access from a separate control plane.
02
Email is untrusted model input. The system narrows its effects with scoped keys, recipient rules, and operator approvals.
Tools and systems
- TypeScript
- Amazon SES
- Amazon S3
- Amazon SNS
- SQLite
- MCP