AI agents can draft contracts, negotiate terms, and manage workflows — but the moment something needs to be physically mailed, the automation breaks. mailbox.bot gives any agent the ability to send real physical mail via MCP, REST API, or A2A.
Physical mail is one of the last gaps in agent capability. An agent can send emails, make API calls, update databases, and trigger webhooks — but sending a physical letter still requires a human. mailbox.bot closes that gap. Add it as an MCP tool, call the REST API directly, or use the A2A protocol. The agent submits a PDF and an address, and a real letter is printed, stamped, and mailed.
Letters, certified mail, postcards, invoices, contracts, legal notices, demand letters, and any PDF document that needs to become physical mail.
MCP: add mailbox-bot as an MCP server and the agent gets a send_mail tool. REST: POST to /api/v1/mail. A2A: use the agent-to-agent protocol. All three produce the same result.
Tracking number, status updates (submitted, printed, mailed, delivered), cost breakdown, and photo proof of the mailed piece — all via API response and webhooks.
Optional. Set requires_approval=true and the letter queues for human review before printing. The human approves from the dashboard; the agent is notified via webhook.
With the $5/mo mailbox plan, the agent also gets a real US mailing address. Inbound mail is scanned and delivered to the agent as structured events — the agent can classify, route, and respond.
Physical mail is a real-world capability that most agents lack. Adding it opens use cases in legal, collections, property management, sales outreach, and compliance that are currently impossible for fully autonomous agents.
MCP for tool-using agents, REST API for direct integration, or A2A for agent-to-agent communication. All three access the same mail infrastructure.
MCP: add 2 lines to your MCP config. REST: use your sk_agent_live_ key. A2A: POST to the A2A endpoint. Setup takes under a minute.
When the workflow requires physical mail, the agent generates a PDF and calls the send_mail tool or API endpoint. We handle printing, postage, and mailing.
Delivery events flow back to the agent via webhooks. The agent can use delivery status to trigger follow-up, update records, or escalate.
The difference is whether the automation breaks when the workflow requires real-world postal mail.
| Dimension | Traditional mail | Agentic mail |
|---|---|---|
| Legal notices | Agent flags the need; a human prints and mails. | Agent sends certified mail directly. Proof is logged automatically. |
| Collections | Agent generates the letter; someone else handles the post office. | Agent sends the demand letter via API. Delivery proof updates the account. |
| Sales outreach | Agent qualifies leads; postcards require a separate tool or vendor. | Agent triggers personalized postcards from the same workflow. |
| Contract delivery | Agent drafts the contract; physical delivery is a manual step. | Agent mails the contract and tracks delivery confirmation. |
| Compliance | Agent detects the requirement; notice mail is a human task. | Agent sends the required notice with certified mail proof. Deadline tracking is automatic. |
Use the deeper proof pages for vertical value. Keep the homepage clean. Let the agentic thesis do the framing.