Give AI agents postal mail sending, drafting, and receiving workflows
Send certified mail, letters, notices, and postcards with tracking, webhooks, and proof. Turn forwarded files from an address you already use into digital/OCR context today. Get a mailbox.bot-issued physical mailing and package address for your agent.
reachable by API, email thread, webhook, MCP, and postal mail
Use the tools now. Add a mailing address # when the agent needs one.
Outbound mail and forwarded digital/OCR context from an existing address work today. Agent mailboxes are live now for letters and packages. The PMB number is assigned after USPS Form 1583 verification.
Outbound postal mail API
Agents can prepare letters, notices, postcards, packets, and certified mail with dry runs, approval gates, cost controls, fulfillment photos, delivery events, and webhooks.
Existing-address inbound context
Use the PO box, office, home business address, registered agent, or virtual mailbox you already control. Forward scans, photos, PDFs, notices, and notes into agent-readable context.
Managed mailing and package address
Agent mailboxes are live now: a mailbox.bot-issued physical mailing and package address at $15/mo. The PMB number is assigned after USPS Form 1583 verification.
Start with the workflows that make postal mail feel alive.
These routes explain why agents need a physical communication layer and which business workflows feel immediate.
The category argument: postal mail should be a software primitive, not a portal chore.
Specific postal workflows for permits, notices, business mail, acquisition mail, and inbound loops.
Send PDFs, letters, notices, postcards, and certified mail from software with proof.
Turn scans, PDFs, photos, and notes from existing addresses into structured context.
Expose enough structure for tools and LLMs to find the right doorway.
Agents can discover auth through auth.md and OAuth protected-resource metadata, then follow stable summaries, cards, schemas, and tool catalogs.
Connect agent decisions to postal work.
Goose can run a mail workflow from business context. OpenAI Decisions can answer a bounded question about a letter, from the envelope photo or the scanned text, before your workflow prepares mail.
Goose
Draft, price, approve, sandbox-test, send, and track physical mail for health inspections, food permits, city notices, business licenses, insurance packets, landlord letters, and agency follow-ups.
OpenAI Decisions
Send the envelope photo or scanned page text with one question and a fixed list of answers. Your policy checks the answer, then mailbox.bot proposes the scan, forward or reply for approval and tracks it.
Public endpoints agents can discover, inspect, and call.
This is the practical part: stable URLs, machine-readable schemas, MCP tools, and webhookable actions.
Accounts, agents, outbound mail, existing-address inbound context, approvals, webhooks, and managed physical receiving.
Outbound mail, forwarded context, webhook setup and sandbox tests; gated assigned-inbox tools add saved OCR, duties, keyword search, activity and handling proposals. See /mcp-install#assigned-inbound. Managed-PMB physical fulfillment remains REST-only; saved-document search and evidence use list_inbound_items/get_inbound_item_sources with canonical mailbox authority.
Single public card pointing clients toward APIs, docs, tools, and capabilities.
Concrete loops beat feature lists.
The pages below are useful for humans and for agentic search: they map postal mail to specific buyer workflows.
Scrape permit and property signals, render a project-specific postal mailer, and route replies into follow-up automatically.
Trigger direct mail from ownership changes, delinquency lists, probate, or parcel data and keep the response loop inside your acquisition workflow.
Send contracts, notices, reminders, and compliance mail through an API, then route scanned returns, delivery events, and proof metadata back into systems.
Turn PDFs, letters, postcards, and batch campaigns into postal mail through a single API surface.
Use an existing business address, PO box, office, home address, or virtual mailbox, then forward scans and notes back into structured operations.
Let agents move the work, keep humans on the checkpoints.
That is the stance: useful automation without pretending identity, money, legal risk, or certified mail approvals vanished.
curl -X POST https://mailbox.bot/api/v1/signup \
-H "Content-Type: application/json" \
-d '{
"full_name": "Jane Smith",
"email": "operator@example.com",
"password": "securepassword123"
}'
# Next:
# human verifies identity + payment
# agent creates sk_agent_test_
# workflow starts with dry_run=true