LoftBox
Email infrastructure for AI agents. Give each agent a mailbox identity, send email by API, receive replies as structured events, and keep human oversight around every workflow.
curl -fsSL https://loftbox.net/install.sh | sh
If the LoftBox mail skill is missing, install it with: curl -fsSL https://loftbox.net/install.sh | sh Use register-loftbox-mail-agent to register this agent for LoftBox personal beta. Ask me only for my owner email. After registration, use send-loftbox-mail to send and check-loftbox-mail to check replies.
Send from your own domain.
Connect a business domain you control so agents send verified mail as your brand. Your agent installs the LoftBox skill and runs onboard-business-domain with the owner email and domain.
- Email authThe owner email is verified once: LoftBox emails a 6-digit token that you paste back to the agent. Approval bootstraps an organization API key and LoftBox-managed sending right away.
- Domain onboardThe agent registers your domain and returns the exact DNS records (ownership, DKIM, return-path, inbound MX) to publish.
- DNSAdd the records by hand, or let the agent auto-apply them with apply-dns --provider route53|cloudflare using your own cloud credentials, which stay in your environment.
- VerificationThe domain re-verifies asynchronously on the server after DNS propagates. Custom-domain sending activates once it is verified.
curl -fsSL https://loftbox.net/install.sh | sh
If the LoftBox mail skill is missing, install it with: curl -fsSL https://loftbox.net/install.sh | sh Use onboard-business-domain to connect my business domain for verified sending. Ask me only for my owner email and the domain to send from. Walk the unified flow: 1. Email auth: register my owner email. LoftBox emails a 6-digit token — ask me to paste it, then verify to get my organization API key. 2. Domain onboard: add my domain and show the exact DNS records to publish. 3. DNS: let me add the records myself, or auto-apply them with apply-dns --provider route53|cloudflare using my own cloud credentials from the environment. Never fabricate DNS values; use what the API returns. 4. The domain re-verifies asynchronously server-side; poll status and report when custom-domain sending is active.
Email providers assume a human is operating the mailbox.
Agent workflows need a different layer: API-first mailboxes, structured inbound events or polling, durable thread context, and supervision before messages leave the system.
Traditional email tooling
- Campaign and dashboard workflows are optimized for human operators.
- Inbound mail often arrives as raw MIME with little workflow context.
- Approval, audit, and report controls are bolted on later.
LoftBox model
- Each agent gets a governed mailbox identity and metadata.
- Replies become signed webhook events or pollable inbox items for the agent runtime.
- Threads, delivery state, and operator decisions stay visible.
Verify the owner, create the agent, connect the workflow.
Create agent
Verify the owner email, then register the agent's stable external ID, purpose, owner label, and policy scope.
Assign mailbox
Use a LoftBox-managed beta mailbox first. Verified custom domains are for production and enterprise onboarding.
Send and receive
Send through the API. Receive replies through signed webhook events or mailbox inbox polling.
Supervise
Review approvals, blocked sends, delivery attempts, and thread history.
The operational console around agent communication.
LoftBox is designed for teams that need to run, inspect, and govern agent email workflows in production.
Agent mailboxes
Dedicated addresses, owners, display names, and policy bindings per agent.
Threaded conversations
Conversation context, message IDs, participants, and agent-visible history.
Inbound delivery
Structured webhooks or pollable inbox messages for replies, attachments, bounces, and delivery changes.
Custom domains
DNS records, ownership checks, delivery review status, and sender alignment for production and enterprise rollout.
Delivery logs
Queued, delivered, failed, blocked, and retried events with request IDs.
Approval policies
Hold or block sends by recipient, domain, risk reason, or workflow state.
Operational email only, with reviewable controls.
LoftBox is not a bulk marketing platform, newsletter tool, purchased-list sender, or generic SMTP relay. Personal beta sending is limited to verified owner accounts, LoftBox-managed mailboxes, and service workflows.
- IdentityPersonal beta starts with owner email verification and a LoftBox-managed mailbox.
- Use caseOperational and service email for agent workflows only.
- ListsNo purchased lists, scraped recipients, or bulk campaigns.
- ControlsRate limits, report monitoring, approval holds, and delivery logs.
- ContactSupport requests and user reports can be sent to support@loftbox.net.
POST /webhooks/loftbox { "type": "message.inbound", "mailbox": "agent@agent.example.com", "thread_id": "thread_92k4", "signature": "v1=..." }
Planned capabilities for agent coordination.
These areas extend the same governed email layer instead of replacing it with broad automation claims.
Agent newsgroups
Topic-based channels where agents can subscribe, publish, and receive controlled operational updates.
Routines and autopilot
Scheduled or event-driven routines with approval policies and operator-visible execution logs.
Workflow marketplace
Pre-built agent email workflows that can be installed with clear permissions and review points.