Question 1

What exactly is mailbox.bot?

Accepted Answer

mailbox.bot gives AI agents the missing real-world postal layer: the ability to receive physical mail and eligible packages at a mailbox address they can use in workflows, publish where a business would list a mailing address, and share with other agents or counterparties. Limited reservations are open today, with agent mailing and package addresses issuing beginning August 31, 2026. Live today, mailbox.bot lets 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.

Question 2

What is an Agent Address?

Accepted Answer

An Agent Address is the public, machine-readable reachability layer for your agent. It can combine the postal address your agent uses in the physical world with email, SMS, webhooks, MCP, and outbound postal mail permissions. Today that postal address can be your business address, PO box, home business address, office, registered agent, or virtual mailbox. Beginning August 31, 2026, reserved mailbox.bot addresses can give approved agents a real mailing and package address for business correspondence, legal mail, eligible package receiving, and rules-based handling.

Question 3

What can we automate today?

Accepted Answer

You can send letters, postcards, notices, and documents through the outbound API today. You can also forward inbound mail context, including photos, scans, PDFs, virtual mailbox notices, and notes, to a private alias for review and outbound follow-up.

Question 4

Can I get a new mailing address for my AI agent?

Accepted Answer

Yes. Reserve a limited spot now; physical mailing and package addresses for AI agents begin issuing August 31, 2026. Expected pricing is $10/mo when the address is available. Before an address is issued, the human owner completes identity verification and a notarized USPS Form 1583 — the standard postal authorization for receiving mail through a commercial mail receiving agency. Your agent can then use that address on forms and workflows, publish or share it as its real-world postal endpoint, receive arrival notifications for new mail and eligible packages, and manage scans, forwarding, holds, routing, and handling rules through the dashboard, API, MCP, and webhooks. Outbound mail and existing-address inbound context are live now.

Question 5

Why use the inbound loop if I already get mail somewhere else?

Accepted Answer

Because your existing address receives mail, but it does not automatically turn that mail into clean software context. mailbox.bot gives you a private forwarding alias so office staff, a virtual mailbox, or your team can forward envelope photos, document scans, PDFs, and notes into one record. OCR and extraction make the inbound item easier for an agent to reason about: who sent it, what it references, what deadline or reply may matter, and which outbound draft should stay linked to it.

Question 6

Why is this better than a traditional mail house or portal?

Accepted Answer

Traditional mail tools usually end with a human uploading files and hoping for the best. mailbox.bot keeps the inbound scan, the outbound draft, the approval step, and the proof of mailing tied to the same workflow so the loop actually closes.

Question 7

How does human oversight work?

Accepted Answer

Humans still handle identity, payment, and any approval gate you want. The agent can organize the workflow and prepare the next action, but outbound mail can pause until a person reviews it in the dashboard.

Give n8n agents and workflows postal mail tools