What Is Mailbox.bot? The Beginner's Guide to Physical Mail for AI Agents
CodexFuse Team · 2026-11-05T12:58:14.468Z · 17 min read min read
What Is Mailbox.bot? The Beginner's Guide to Physical Mail for AI Agents
What Is Mailbox.bot?
If you are asking what is mailbox.bot, the short answer is that it is a mailing address and postal-mail API for AI agents. It gives an agent a real US street address — 2100 N Sepulveda Blvd, STE 28, Manhattan Beach, CA 90266 — plus the tools to receive letters and packages and to send physical mail without a human visiting a post office. In short, it is the postal adapter that lets software touch paper.
Every webhook event Mailbox.bot sends is signed with HMAC-SHA256, so your agent can verify that a mail notification really came from the service. You can check how that signature scheme works with a free SHA-256 hash generator. The signature is the first line of defense against fake mail events.
Mailbox.bot runs as a hosted service, so there is nothing to install on your own server. That is the same trade-off you make with VPS hosting: a VPS gives you full control of a machine, while a hosted service like Mailbox.bot gives you one job done for you. This guide explains when the hosted route wins.
| Fact | Detail |
|---|---|
| What it is | Mailing address and postal-mail API for AI agents |
| Street address | 2100 N Sepulveda Blvd, STE 28, Manhattan Beach, CA 90266 |
| Inbound mail | Signed webhooks with sender line, page counts, and fetch URLs |
| Outbound mail | MCP send_outbound_mail or POST /v1/mail; staff print, stuff, stamp, and mail |
| Starting price | One-page First-Class letter from $2.00; no monthly mailbox price stated |
| Released | May 2, 2026 (PulseMCP); resurfaced on Show HN November 5, 2026 |
Searches for mailbox.bot ai agents land on the vendor's own pages first. No independent explainer, review, or guide exists as of November 5, 2026 — only the vendor site, its API docs, a PulseMCP listing, and the Show HN feed entry.
Why Would an AI Agent Need a Mailing Address?
AI agents can already send email, write code, and make phone calls. They cannot open a tax notice, sign for a package, or send a certified letter — paper is the one surface they cannot reach. A mailing address for AI agents closes that gap.
The vendor's own examples make the gap concrete: a tax or payroll portal sends an activation code by post, and the agent cannot finish setup until a human reads the letter. The same problem shows up with IRS notices, 1099s for a CPA, and paper bills that need to become drafts in QuickBooks or Bill.com.
Mailbox.bot answers by turning paper into data an agent can act on. Inbound mail becomes scans, OCR text, and webhook events, while outbound mail becomes an API call. The agent never touches an envelope.
How Inbound Mail Works: From Envelope to Webhook
Inbound mail starts at the staffed Manhattan Beach facility, where each mailbox is a virtual mailbox at a real street address, not a PO Box. Carriers accepted there include USPS, FedEx, UPS, DHL, Amazon, OnTrac, LaserShip, and GSO. Every item is logged on arrival with its carrier, tracking number, and weight.
- Mail arrives at 2100 N Sepulveda Blvd and is logged with carrier, tracking, and weight.
- Your webhook receives a small signed JSON event with the sender line, the letter or package type, page counts, and two URLs.
- Your agent fetches the page text and images with its API key — they never travel inside the webhook payload.
- Keyword rules route each company's mail to the agent or endpoint that handles it.
The signature matters. Each event is signed with HMAC-SHA256 under the Standard Webhooks v1 format, so your agent can reject forged events. Page text and images stay behind the API on purpose: the webhook only carries the sender line, page counts, and fetch URLs.
| Webhook event | What it means |
|---|---|
| inbound.received | A letter or package arrived and was logged |
| inbound.action.requested | An action on a piece of mail was requested |
| inbound.action.completed | The requested action finished |
| inbound.pages_ready | Scanned pages are ready to fetch |
| inbound.keywords_matched | A keyword rule matched and routed the item |
You can also feed Mailbox.bot from an address you already have. Forward envelope photos, opened-mail photos, PDFs, virtual-mailbox notices, and notes to a private alias, and your agent organizes the inbound context. The vendor calls this bridging the paper surface area of the world into agent-readable context.
How Outbound Mail Works: From API Call to Mailbox
Outbound mail starts with one of two calls: the MCP tool send_outbound_mail, or POST /v1/mail over REST. You pass a document, a recipient, and a mail class. Together they form a physical mail api ai agents can call like any other tool.
Facility staff then print, stuff, stamp, and mail every letter by hand. The vendor says its team photographs every piece — the outside of the envelope with the enclosed documents visible — and logs it with carrier tracking numbers. Postage is applied through USPS or FedEx, with UPS also available per the API docs.
The lifecycle is visible through webhooks: mail.pending_approval, mail.submitted, mail.ready, mail.mailed, and mail.delivered. Sent mail stays searchable in the dashboard or through GET /v1/mail by recipient, address, tracking number, or date.
Documents can be PDF, DOCX, JPG, PNG, TXT, or CSV, up to 10 MB each, and PDF is treated as WYSIWYG. Agents and software can send letters, certified mail, document packets, notices, postcards, and batch mail through the dashboard, REST API, MCP, and webhooks.
What Does Mailbox.bot Cost?
Mailbox.bot charges for outbound mail with prepaid credits, and the pricing is unusually transparent for the category. A one-page USPS First-Class letter starts at $2.00, with extra pages adding per-page printing and any extra postage from weight. No monthly mailbox subscription price is stated on the homepage or in the API docs, so do not budget for one until the vendor publishes it.
| Item | Price |
|---|---|
| One-page First-Class letter | From $2.00 |
| Black-and-white printing | $0.40 per page |
| Color printing | $0.70 per page |
| Priority, one-page floor | $15.00 |
| Certified, one-page floor | $20.00 |
| Certified plus Return Receipt, one-page floor | $24.00 |
The gaps between the floors are easy to check. Certified mail at $20.00 costs ten times the $2.00 First-Class baseline, and adding a return receipt costs $4.00 more, taking Certified from $20.00 to $24.00. Color printing costs $0.30 more per page than black and white ($0.70 minus $0.40), and that $0.40 black-and-white page is 20 percent of the $2.00 letter.
The vendor's own worked example keeps the math honest: a 6-page Certified letter with Electronic Return Receipt costs $26.29 in total. That is $2.50 handling plus $2.40 printing at $0.40 a page plus $21.49 postage minus a $0.10 promotional discount, for a 1.43 oz piece. The arithmetic adds up exactly, which is the point of a dry run.
Volume discounts reward big sends: 5 percent off at 500 pieces, 10 percent at 1,000, and 15 percent at 5,000. At the $2.00 baseline, 500 letters cost $1,000 before discount and $950 after the $50 saving; 1,000 letters cost $2,000 before discount and $1,800 after the $200 saving; 5,000 letters cost $10,000 before discount and $8,500 after the $1,500 saving.
FedEx carries its own adjustments: FedEx 2Day includes a fixed $8.00 reduction, while FedEx Overnight adds a fixed $18.00. Signature add-ons run from $5.00 to $11.00 depending on the service. Your agent can read the live credit balance through GET /v1/credits, and a send that exceeds the balance returns a 402 response with the exact shortfall in cents.
The Safety Rails: Approval Gates and Cost Caps
An agent that can send physical mail on its own is a risk, and Mailbox.bot answers with seven safeguards that the vendor documents. The most important is the human approval gate: setting requires_approval=true creates a pending review item with a document preview, and no credits are spent until a member approves it in the dashboard. Sensitive mail can pause for human review before live fulfillment.
Cost caps work the same way. The X-Max-Cost-Cents header sets a hard ceiling — 1500 means $15.00 — and a request whose computed cost exceeds it is rejected with a 422 before any credits are spent and before any facility work starts. A dry run with dry_run=true returns the exact cost breakdown without creating a record or spending anything.
The remaining rails cover the edges: test keys (sk_agent_test_) run against production endpoints with real validation and cost previews but zero credit debits; platform per-transaction and daily spend limits are enforced server-side; and recent exact or near-duplicate live submissions are rejected with a 409. A sent item can still be cancelled with DELETE /v1/mail/:id before printing starts, and eligible credits are returned once.
What Is USPS Form 1583, and Why Does an Agent Need a Human Behind It?
Every Mailbox.bot address requires USPS Form 1583, titled Application for Delivery of Mail Through Agent. The form authorizes a Commercial Mail Receiving Agency to receive and handle mail on your behalf, and without it on file the post office will not deliver your mail to the agency. Your mailbox number is assigned only after verification.
The form demands two forms of identification — one government-issued photo ID and a second document confirming the address — plus a witnessed signature. USPS requires Form 1583 to be signed before a notary with two forms of ID, so a verified human stands behind every agent mailbox; the vendor says the online notary session is available and its fee is waived. Note the nuance: USPS rules also permit signing in front of the agency's own staff, so the notary is one of two witnessing paths, not the only one.
The rule exists to stop anonymous mailboxes. Form 1583 creates a verified, auditable link between a real, identified human and each private mailbox number, which is why virtual-mailbox providers route every customer through it. An agent gets a postal identity only because a human vouches for it.
Which AI Tools Work With Mailbox.bot?
Mailbox.bot is harness-agnostic: it works through MCP, REST, A2A, and webhooks, so any agent framework that speaks one of those can use it. The vendor names OpenClaw, Cursor, Devin, Codex, and Hermes for quickstart, and LangChain, AutoGen, CrewAI, Goose, OpenAI Agents SDK, Vercel AI SDK, and LlamaIndex for framework integration. If you want to learn how to use Claude Code with an MCP tool like this one, start there and add the mailbox server to its config.
MCP, the Model Context Protocol, is an open-source standard for connecting AI applications to external systems. The official docs describe it as a USB-C port for AI applications: just as USB-C gives a standard way to connect devices, MCP gives a standard way to connect AI applications to data sources, tools, and workflows. Mailbox.bot acts as the MCP server; your Claude, ChatGPT, Cursor, or Copilot acts as the client.
The vendor says that if a developer gives Cursor, Claude Code, or another LLM agent only an API key plus the /api-docs page, the agent can answer billing and order-control questions over REST. That is the test of a genuinely agent-readable API: no human needs to translate the docs first.
Rate limits are generous for an agent workflow: 100 requests per minute per API key, which is 6,000 requests an hour. Custom limits exist for enterprise use. Key types separate concerns — member keys (sk_live_) hold full access, agent keys (sk_agent_) are scoped to one agent, and facility keys (sk_facility_) cover the staff side.
Mailbox.bot vs Virtual Mailbox Services
Mailbox.bot is often compared with virtual mailbox services, and the comparison is fair — all three live in the same Form 1583 world. The difference is the customer: iPostal1 and Anytime Mailbox serve humans and businesses through an app, while Mailbox.bot serves AI agents through an API. That one difference changes almost everything else.
| Feature | Mailbox.bot | iPostal1 | Anytime Mailbox |
|---|---|---|---|
| Built for | AI agents (agent-first) | Humans and businesses | Humans and businesses |
| Receiving address | Real street address, 1 live facility (Manhattan Beach, CA); Nevada and Utah planned | Real street address, 4,250+ locations | Real street address, about 2,500 locations |
| Inbound mail | Signed webhooks, sender line, page counts, fetch URLs; OCR pages via API | Envelope photo in app; request scan, forward, or shred | Envelope image in app; request scan, forward, or shred |
| Outbound mail | Yes — print, stuff, stamp, and mail via API or MCP; fulfillment photos; USPS, FedEx, UPS | No outbound print-and-mail | No outbound print-and-mail |
| Agent integration | MCP (send_outbound_mail), REST (POST /v1/mail), A2A, webhooks | None (app and web dashboard) | None (app and web dashboard) |
| Starting price | Free tier per PulseMCP; outbound from $2.00 per one-page First-Class letter; no mailbox subscription price stated | From $9.99 a month (personal) | From about $4.99 to $9.99 a month depending on location |
| Form 1583 | Required; online notary, fee waived (vendor-stated) | Required; online notary $25 (vendor-stated) | Required; online notarization available |
The scale difference runs the other way. iPostal1 lists over 4,250 real street addresses, and Anytime Mailbox lists around 2,500, while Mailbox.bot operates from one staffed facility in Manhattan Beach. A human who wants a local address in another city picks a virtual mailbox; an agent that wants to send certified letters picks Mailbox.bot.
Prices tell the same story. iPostal1 starts at $9.99 a month for a personal address and $14.99 for a business address, and Anytime Mailbox starts around $4.99 to $9.99 a month depending on the location. Mailbox.bot states no monthly mailbox price at all and charges per piece instead, starting at $2.00 for a one-page First-Class letter.
You pay for the address with the virtual mailbox services, and you pay for the mail with Mailbox.bot.
When Mailbox.bot Fits — and When It Does Not
Mailbox.bot fits when your agent's work ends on paper. Tax notices, certified demand letters, compliance filings, permit postcards, invoices, and lease notices are the vendor's own examples, and they share one trait: the recipient expects paper, and the paper needs proof. A signed webhook plus a fulfillment photo is the proof.
| Use Mailbox.bot when | Use something else when |
|---|---|
| Your agent must send certified or demand letters with proof of mailing | You only need a person to read scanned mail in an app |
| A tax, legal, or compliance notice must reach a real address | You need a local address in a city other than Manhattan Beach |
| You want every send gated by human approval and a cost cap | You want the cheapest inbound-only mailbox and never send mail |
| Your agent already works through MCP or REST | Your workflow is email-only and paper never enters it |
| You send batch mail and want volume discounts | You need mail outside the United States |
It does not fit when the job is inbound-only and human. If a person just needs a local address to receive mail and read scans in an app, a virtual mailbox service with thousands of locations is cheaper and closer. It also does not fit outside the United States: the one live facility is in California, and Nevada and Utah locations are planned, not live.
There is also a sibling pattern worth knowing. If your agents share memory rather than mail, what beacon.sh is explains the coding-agent memory layer that keeps context across Claude Code, Codex, and Cursor sessions. Memory and mail solve different edges of the same problem: agents that need to persist what they learn and reach what they cannot touch.
And if the protocol layer interests you, what MCP over MOQT is explains how MCP traffic can ride a modern media transport. Mailbox.bot itself uses plain MCP over Streamable HTTP, so the MOQT variant is a future direction, not a requirement.
How to Set Up Mailbox.bot in 6 Steps
Setup takes an account, a verified identity, and one API key. The vendor's signup flow has no CAPTCHA, and the agent-callable signup endpoint creates a human-owned account and returns a checklist. These six steps follow the vendor's own flow.
- Create your account and verify your phone number.
- Request a mailing address through POST /api/v1/mailing-address-requests and keep the lead_id it returns.
- Complete USPS Form 1583 in the online notary session and receive your mailbox number.
- Add prepaid credits and set your per-transaction and daily spend limits.
- Connect your agent through MCP or REST with an agent-scoped key (sk_agent_).
- Send a dry run with dry_run=true, check the cost breakdown, then send your first live letter with requires_approval=true.
Test first with a test key. Test keys (sk_agent_test_) work on production endpoints with real validation, real cost previews, and signed webhooks, but zero credit debits. Swapping the test key for a live agent key is the only change needed to go live.
What Mailbox.bot Is Not
Mailbox.bot is not a November 2026 launch. PulseMCP lists its release date as May 2, 2026, and the November 5, 2026 trigger is a Show HN post — the product resurfaced, it did not launch. That is 187 days between release and the Show HN appearance, and the distinction matters for anyone judging how mature the service is.
It is not a general web host or a VPS, and it is not an email service. It handles ai agent postal mail only — letters, certified mail, document packets, notices, postcards, and batch mail — and it does not send or receive email. Related email-for-agents products like Mailgent, Tinbox, and Bird Agent Mailboxes solve a different problem.
It is not yet a multi-location network. Only the Manhattan Beach facility is live, and the Nevada and Utah locations are planned with no city, address, or date published. It is also not a product with published customer counts, mail volumes, or uptime figures — none are stated on the vendor's pages.
Judge it on its documented API and pricing, not on numbers that do not exist.
Sources
Mailbox.bot homepage — mailbox.bot (vendor, fetched November 5, 2026).
Mailbox.bot API docs — mailbox.bot/api-docs (vendor pricing and safeguards, fetched November 5, 2026).
PulseMCP listing — pulsemcp.com/servers/mailbox-bot (release date May 2, 2026; fetched November 5, 2026).
Show HN daily feed — showhn.buzzing.cc (November 5, 2026 listing; fetched November 5, 2026).
Model Context Protocol docs — modelcontextprotocol.io (MCP definition; fetched November 5, 2026).
iPostal1 plans — ipostal1.com (fetched November 5, 2026).
StartupOwl iPostal1 review — startupowl.com/reviews/ipostal1 (updated September 26, 2026).
StartupOwl Anytime Mailbox review — startupowl.com/reviews/anytime-mailbox (updated November 3, 2026).
USPS Form 1583 guide — registate.net (fetched November 5, 2026).
Frequently Asked Questions
What is Mailbox.bot?
Mailbox.bot is a mailing address and postal-mail API for AI agents. It gives an agent a real street address in Manhattan Beach, California, plus signed webhooks for inbound mail and an MCP or REST API for outbound mail. Facility staff print, stuff, stamp, and mail every letter.
How much does it cost to send a letter with Mailbox.bot?
A one-page USPS First-Class letter starts at $2.00, with black-and-white printing at $0.40 a page and color at $0.70. Certified mail starts at $20.00 for one page, and Certified with Return Receipt starts at $24.00. No monthly mailbox subscription price is stated, and a dry run shows the exact cost before you spend anything.
Does Mailbox.bot need USPS Form 1583?
Yes. Your mailbox number is assigned only after USPS Form 1583 verification, signed before a notary with two forms of ID. The vendor says the online notary session is available and its fee is waived.
A verified human stands behind every agent mailbox.
Can my AI agent send mail without my approval?
Only if you let it. Setting requires_approval=true pauses every send for human review in the dashboard, and the X-Max-Cost-Cents header caps the spend per request. Test keys let an agent practice with zero credit debits.
Is Mailbox.bot a new product?
No. PulseMCP lists its release date as May 2, 2026, and it appeared on Show HN on November 5, 2026 — 187 days later. The November attention is a re-surface, not a launch.
