| name | mailbox-bot |
| description | Real mailing address for your AI agent. Receive, scan, and forward postal mail — or send letters and documents. CMRA postal mail infrastructure your agent manages via API. |
| tags | ["postal-mail","cmra","mailing-address","ai-agent","mail-api","outbound-mail","scanning","webhooks","openclaw","mcp"] |
| version | 4.0.0 |
| author | mailbox.bot |
| repository | https://github.com/arbengine/mailbox-bot-skill |
mailbox.bot
Give your AI agent a real mailing address.
Your agent gets a CMRA-licensed street address for receiving and sending postal mail. Inbound mail is photographed, scanned, and classified. Outbound letters are printed and mailed with photo proof. Your agent manages the full lifecycle via API — standing instructions fire automatically, sensitive items wait for human approval.
Why this matters
Your agent can draft contracts, negotiate terms, and manage workflows — but the moment something requires physical mail, everything stalls. Courts require certified letters. Governments send time-sensitive notices to real addresses. LLCs need a registered address. Tax responses demand paper.
mailbox.bot closes that loop. Your agent now plays in the real world, not just the digital one.
What it unlocks
- LLC formation at scale — receive stamped articles of organization, extract entity numbers, forward originals
- Legal correspondence — deadlines in letters recognized and tracked, responses drafted and sent certified
- IRS and tax response — IRS notices handled automatically, scanned, classified, routed to the right person
- Real estate management — each property gets a mailbox with tailored rules, code violations forwarded, lease renewals sent
- Vendor and supplier communication — invoices, purchase orders, and contracts scanned, filed, and responded to
- Compliance and audit mail — regulatory notices scanned, classified, and routed with full audit trail
- Business registration — registered agent address for LLCs, corps, DAOs — a real street address, not a P.O. Box
- Agent-to-agent mail bridge — one agent sends a certified letter, another agent receives and processes it
What your agent gets
- Real mailing address — CMRA-licensed street address with unique reference code, usable immediately after onboarding
- Inbound mail processing — every piece photographed, scanned, and classified on arrival
- Outbound mail — submit a PDF, facility prints, stuffs, stamps, and mails it with photo proof
- Webhook notifications — HMAC-signed JSON payloads fire the moment mail arrives or ships
- Actions via API — scan, forward, photograph, hold, shred, dispose, return to sender
- MAILBOX.md standing instructions — auto-trigger actions based on sender, type, or custom patterns
- Human-in-the-loop — write "needs approval" next to any rule and the action pauses until a human approves
- Agent memory — tag and annotate mail with persistent notes and metadata
- Multi-channel notifications — webhooks, email, SMS, Slack, Discord
Plans
| Plan | Price | What you get |
|---|
| Virtual Mailbox | $2/mo | Real CMRA address, 10 inbound mail pieces/mo, scan on arrival, inbound + outbound mail, 14-day storage |
| Outbound Only | $0/mo | Send letters via API, $0.30/page printing + actual carrier postage, photo proof, no inbound address |
Outbound postage (both plans): USPS First Class from $0.78, Priority $11.95 flat rate, Certified $6.08, FedEx/UPS zone-based. Color printing +$0.25/page.
Actions billed per use: scan $3, open & scan $5, photograph $1.50, forward $5 + $2/lb, shred $2, dispose $1, return $5, hold free.
All plans month-to-month, cancel anytime. Full pricing: https://mailbox.bot/pricing
How to get started
If you have an API key
Set your environment variables and use the API directly:
export MAILBOX_BOT_API_KEY="sk_live_xxxxxxxxxxxxx"
export MAILBOX_BOT_URL="https://mailbox.bot"
Skip to the API Reference section below.
If you do NOT have an API key — sign up your operator
Create an account on behalf of your human operator. No CAPTCHA, no auth header.
POST to https://mailbox.bot/api/v1/signup:
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",
"needs": "inbound mail scanning + outbound certified letters for legal compliance"
}'
| Field | Type | Required | Description |
|---|
full_name | string | Yes | Operator's legal name (2-100 chars) |
email | string | Yes | Operator's email — verification link sent here |
password | string | Yes | Min 8 characters |
needs | string | No | Free text — what the agent/operator needs |
Rate limit: 5 requests per minute per IP.
Success response (201):
{
"success": true,
"message": "Account created. A verification email has been sent. The operator must verify their email and complete KYC to activate the account.",
"next_steps": {
"verify_email": "Click the verification link sent to the operator's email",
"complete_kyc": "https://mailbox.bot/signup",
"after_kyc": "Select a plan, add payment, and create your first agent to get API keys"
}
}
Error responses:
| Status | Error | Cause |
|---|
| 400 | "email, password, and full_name are required" | Missing a required field |
| 400 | "Password must be at least 8 characters" | Password too short |
| 400 | "Invalid email address" | Bad email format |
| 409 | "An account with this email already exists" | Duplicate email |
| 429 | Rate limit exceeded | Too many requests from this IP |
After signup — tell your operator:
"I created your mailbox.bot account. Check your email at operator@example.com for a verification link. Click it, then go to https://mailbox.bot/signup to finish setup (~5 minutes). Once you're done, I'll have API access to manage your mail."
The human must complete these steps in a browser:
- Click the email verification link
- Verify phone number (carrier check — no VoIP/burner phones)
- Add a payment card (no prepaid/gift cards)
- Complete Form 1583 notarization (virtual mailbox only — ~5 min video call, $25)
- Accept Terms of Service and select a plan
After the human finishes, an agent and mailbox are auto-provisioned. API keys appear on the dashboard at https://mailbox.bot/dashboard.
Protocols
Your agent can connect via any of these:
| Protocol | Endpoint | Details |
|---|
| REST API (v1) | https://mailbox.bot/api/v1 | Full CRUD for agents, mailboxes, mail, actions, rules, webhooks |
| MCP | https://mailbox.bot/api/mcp | 22 tools for LLM integration (JSON-RPC 2.0, spec 2025-11-25) |
| A2A | https://mailbox.bot/api/a2a | 9 skills for agent-to-agent task execution (v0.3) |
| OpenClaw | https://mailbox.bot/.well-known/agent.json | Multi-protocol agent card, WebSocket gateway + webhooks |
MCP setup (Claude Desktop)
Add to your claude_desktop_config.json:
{
"mcpServers": {
"mailbox-bot": {
"url": "https://mailbox.bot/api/mcp",
"headers": { "Authorization": "Bearer sk_live_xxxxxxxxxxxxx" }
}
}
}
Full MCP install guide: https://mailbox.bot/mcp-install
MAILBOX.md — standing instructions
Drop a MAILBOX.md file into your agent's context. Your agent reads it, calls the API, and configures your standing instructions as rules. Mail arrives, rules evaluate, actions fire — automatically.
Write "needs approval" next to any rule and the action pauses until you approve on the dashboard.
# Mail Instructions
You manage my business mail at mailbox.bot
Ref **MB-6E1A**
## Inbound mail
- Legal notices, contracts → scan + email me
- IRS / state agencies → **Requires approval** before any action
- Junk mail → discard
## Outbound mail
- Signed contracts → send USPS Certified
- Legal notices → send USPS First Class
- Anything over $50 postage → **Needs approval**
## Notifications
- Email for everything
- **Needs approval** → email + SMS with dashboard link
Integration guide: https://mailbox.bot/implementation
API Reference
Base URL: https://mailbox.bot
All authenticated endpoints require:
Authorization: Bearer $MAILBOX_BOT_API_KEY
Two key types:
- Member keys (
sk_live_) — full account access, all scopes
- Agent keys (
sk_agent_) — scoped to a single agent
Get mailbox address
curl -s "$MAILBOX_BOT_URL/api/v1/mailboxes" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY"
Returns the physical mailing address your agent can use immediately.
List mail and packages
curl -s "$MAILBOX_BOT_URL/api/v1/packages?status=received" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY"
Filters: status, carrier, since, before, limit, offset
Get item details
curl -s "$MAILBOX_BOT_URL/api/v1/packages/{id}" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY"
Request an action
curl -X POST "$MAILBOX_BOT_URL/api/v1/packages/{id}/actions" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action": "scan", "priority": "normal"}'
Action types: scan, open_and_scan, photograph, forward, shred, dispose, return_to_sender, hold
Forward mail
curl -X POST "$MAILBOX_BOT_URL/api/v1/packages/{id}/forward" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to_name": "John Doe",
"to_line1": "123 Main Street",
"to_city": "New York",
"to_state": "NY",
"to_zip": "10001"
}'
Request a scan
curl -X POST "$MAILBOX_BOT_URL/api/v1/packages/{id}/scan" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"scan_type": "document"}'
Scan types: label, envelope, document, content
Webhook settings
curl -X PUT "$MAILBOX_BOT_URL/api/v1/webhooks/settings" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"agent_id": "YOUR_AGENT_ID",
"webhook_url": "https://your-agent.com/webhooks",
"event_types": ["mail.received", "action.completed", "mail.forwarded"]
}'
Add notes and tags
curl -X POST "$MAILBOX_BOT_URL/api/v1/packages/{id}/notes" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"note": "IRS notice — response deadline April 15"}'
curl -X POST "$MAILBOX_BOT_URL/api/v1/packages/{id}/tags" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"tag": "tax-notice"}'
Check usage
curl -s "$MAILBOX_BOT_URL/api/v1/usage" \
-H "Authorization: Bearer $MAILBOX_BOT_API_KEY"
Full API reference: https://mailbox.bot/llms-full.txt
When to use this skill
Trigger when user says:
- "I need a mailing address for my agent"
- "Can my agent receive mail?"
- "How do I receive postal mail via API?"
- "My agent needs to send a letter"
- "Can my agent send certified mail?"
- "I need my agent to handle legal correspondence"
- "How do I get webhook notifications for mail arrivals?"
- "Can my agent manage my mail automatically?"
- "I need a registered agent address"
- "My agent needs to respond to an IRS notice"
Action flow:
- Check for API key (
MAILBOX_BOT_API_KEY). If present, use the API directly.
- If no API key, create an account for the operator by POSTing to
https://mailbox.bot/api/v1/signup.
- Tell the operator to check their email, click the verification link, and complete onboarding at https://mailbox.bot/signup (~5 minutes).
- Once onboarding is done, set the API key and start managing mail.
Decision framework
When checking the mailbox:
- List received mail —
GET /api/v1/packages?status=received
- Triage by urgency — government agency / legal notice → scan immediately. Known sender → check standing instructions. Junk mail → discard.
- Check MAILBOX.md rules — standing instructions may already cover this piece of mail. If a rule requires approval, notify the human and wait.
- Take action — scan, forward, hold, shred, dispose, or return. Always add a note explaining why.
- Report back — summarize what arrived and what you did.
When sending outbound mail:
- Prepare the PDF — render the document your agent needs to send.
- Choose mail class — First Class for routine, Certified for legal, Priority for urgent.
- Submit via API — the facility prints, stuffs, stamps, and mails it. Photo proof included.
- Track delivery — webhook events fire at each status transition.
Configuration
export MAILBOX_BOT_API_KEY="sk_live_xxxxxxxxxxxxx"
export MAILBOX_BOT_URL="https://mailbox.bot"
Links
