Verified-domain operational email

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.

Per-agent email identity on a verified custom domain.

Outbound API and inbound webhook events.

Thread context preserved across conversations.

Approval policies, delivery logs, and abuse controls.

Request access View docs

agent-mailbox verified

Mailbox

support-agent@company.com

delivered

Inbound event

message.reply.received

queued

TXT lb-domain-verify=7d4c2a19b6 Copy

CNAME mail.company.com -> inbound.loftbox.net Copy

Problem

Email providers assume a human is operating the mailbox.

Agent workflows need a different layer: API-first mailboxes, structured inbound events, 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 abuse controls are bolted on later.

LoftBox model

Each agent gets a governed mailbox identity and metadata.
Replies become signed webhook events for the agent runtime.
Threads, delivery state, and operator decisions stay visible.

How it works

Create the agent, verify the domain, connect the workflow.

Create agent

Assign mailbox

Use a verified custom domain and mailbox address for operational email.

Send and receive

Send through the API. Receive replies through signed webhook events.

Supervise

Review approvals, blocked sends, delivery attempts, and thread history.

Product surfaces

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.

mailboxes.create

Threaded conversations

Conversation context, message IDs, participants, and agent-visible history.

threads.retrieve

Inbound webhooks

Structured events for replies, attachments, bounces, and delivery changes.

webhooks.deliver

Domain verification

DNS records, ownership checks, provider review status, and sender alignment.

domains.verify

Delivery logs

Queued, delivered, failed, blocked, and retried events with request IDs.

events.list

Approval policies

Hold or block sends by recipient, domain, risk reason, or workflow state.

policies.evaluate

Trust and provider review

Operational email only, with reviewable controls.

LoftBox is not a bulk marketing platform, newsletter tool, purchased-list sender, or generic SMTP relay. Sending is limited to verified domains and service workflows.

DomainsOutbound mail requires verified ownership and DNS alignment.
Use caseOperational and service email for agent workflows only.
ListsNo purchased lists, scraped recipients, or bulk campaigns.
ControlsRate limits, abuse monitoring, approval holds, and delivery logs.
ContactAbuse reports can be sent to abuse@loftbox.net.

delivery-log thread_92k4

09:41:02 Policy evaluated: operational support reply verified

09:41:03 Message accepted for delivery queued

09:41:07 Provider confirmed recipient delivery delivered

09:44:15 Reply received and webhook signed pending

POST /webhooks/loftbox
{
  "type": "message.reply.received",
  "mailbox": "support-agent@company.com",
  "thread_id": "thread_92k4",
  "signature": "v1=..."
}

Network layer roadmap

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.