Physical mailing addresses
for AI agents

mailbox.bot enables an AI agent to be associated with a physical mailing address and reached in the real world. It is an early step toward giving an agent practical form and a shareable identity surface, unlocking trust and scalability. The result is a place humans, businesses, and other agents can interact with through mail, documents, notices, and eligible packages. Live today: agents and software send certified mail, letters, notices, document packets, and postcards by dashboard, REST API, or MCP, and turn mail from an address you already use into structured context by forwarding photos, scans, PDFs, and notes. Separately, reservations are open for mailbox.bot-issued street addresses with mailbox numbers for approved accounts after identity verification, USPS Form 1583 where required, and facility approval.Enable your agent to share a real, reachable address.

Yes. A verified human or business owner can reserve a real postal mailing and package address for an AI agent: a physical street-address surface with a mailbox number that the verified owner controls and the agent can monitor. Today, that address can be a business address, PO box, home business address, office, registered agent, or virtual mailbox; mailbox.bot is live for outbound physical mail and existing-address inbound context. For a mailbox.bot-issued street address plus mailbox number, reservations are open; approved accounts begin receiving addresses August 2026 after identity verification, USPS Form 1583 where required, and facility approval. The agent can monitor scans, photos, PDFs, inbound context, and eligible package events, then draft or send outbound replies through MCP/API workflows with rules, webhooks, approvals, sandbox keys, tracking, proof, and audit events. Example format: Attn: My Hermes Agent, Mailbox #128, 123 Main St, Torrance, CA 90502. This is example copy only, not an address issued today.

Today, mailbox.bot supports outbound physical mail and inbound context from scans, PDFs, photos, virtual mailbox notices, provider notices, notes, and existing addresses. Agents and software can send letters, certified mail, document packets, notices, postcards, and batch mail through the dashboard, REST API, MCP, A2A, and webhooks.

Most teams spend money at the paper edge: checking mailboxes, opening envelopes, scanning pages, naming PDFs, copying details into a CRM, emailing status updates, printing replies, buying postage, and chasing proof. mailbox.bot turns that paper surface area into workflow context. Physical mail, packages, email, phone, CRM, ticketing, and correspondence systems can connect through scans, OCR, extracted fields, MCP/API replies, webhooks, approvals, tracking, proof, and audit events, so the full chain becomes observable and traceable instead of stitched together by hand.

Eligible package workflows are part of the managed receiving-address product and follow the same approved address-issuance path. Today, agents can still use mailbox.bot for outbound physical mail and inbound context from scans, PDFs, photos, notes, and addresses the operator already controls.

mailbox.bot bridges the paper surface area of the world into agent-readable context. A physical street address or existing address can produce arrival photos, scans, OCR, extracted fields, package events, and inbound context. The agent or workflow can use that context to draft the next email, phone follow-up, CRM update, support ticket, legal response, certified letter, package action, or outbound postal reply.

Yes. mailbox.bot is designed so physical street addresses, receiving workflows, outbound mail, and packages can wire into the same systems that already manage email, phone calls, CRM records, tickets, documents, and correspondence. MCP/API tools handle the agent actions; webhooks, approvals, sandbox keys, tracking, delivery proof, photos, and audit events make the physical chain observable and traceable.

The agent can classify the mail, extract entities and deadlines, connect it to a CRM or ticket, draft a response, request approval, send outbound mail, and preserve the full lineage from inbound scan to outbound proof and webhook events.

Yes. mailbox.bot is harness-agnostic. OpenClaw, Hermes, LangChain, AutoGen, CrewAI, Goose, OpenAI Agents SDK, Vercel AI SDK, LlamaIndex, custom workers, and other AI agent harnesses can use mailbox.bot through MCP, REST API, A2A, OpenClaw discovery, and webhooks. The preview name "My Hermes Agent" is an example, not a requirement. Outbound physical mail and existing-address inbound context are live today.

MCP server lets AI agents send physical mail. With mailbox.bot MCP tools, an agent can prepare outbound letters and certified mail, run sandbox tests, apply human approval gates, receive webhook events, and use inbound scans or PDFs as context for replies.

The agent can add mailbox.bot as an MCP server, call the REST API, use A2A, or trigger a dashboard-approved workflow. It submits the document, recipient address, mail class, metadata, cost controls, and approval policy. mailbox.bot then handles print, postage, mail handoff, tracking, and webhook events.

It can. Use requires_approval=true, key-level force approval, sandbox keys, dry runs, and max-cost headers to keep agents from sending or spending without the operator's policy. Sensitive mail can pause for human review before live fulfillment.

Email forwarding intake and outbound access start at $0/mo. A 1-page First Class letter is a $1.00 flat price; other mail is $2.50 handling + $0.40/page printing + actual carrier postage, with color printing at +$0.25/page. Reserved mailbox.bot-issued mailing and package addresses are planned at $10/mo for approved accounts.

No. You can manage the workflow from the dashboard, then add API calls or webhooks when you are ready. Teams that want automation can connect immediately, and teams that prefer a UI can start there and grow into the API later.