Humans usually need the workflow story first. Agents usually need public machine-readable entry points. This page bridges both, so discovery does not depend on a single homepage paragraph.
Category framing and the operator-level argument for why postal mail belongs inside a software workflow.
A hub page for the vertical guides most likely to be cited by humans, agents, and search surfaces.
Best entry point when the immediate need is printing and mailing letters, postcards, and documents via API.
Best entry point when the workflow needs a real receiving address and scanned postal mail routed back into software.
Curated summary for LLMs, search agents, and RAG pipelines.
Capability inventory plus discovery pointers and plans.
Shortest public path from discovery to first API call.
Multi-protocol agent card with the main machine-readable entry points.
Standard A2A well-known path used by registries, SDKs, and agent discovery crawlers.
Machine-readable REST schema for codegen, validation, and browsing tools.
Public tool catalog for MCP-aware agents and clients.
Public MCP server source for developers, registries, and repo-aware coding agents.
Public skill repo that explains installation, metadata, and marketplace discovery.
POST three fields to /api/v1/signup. No CAPTCHA, no auth header, no TOS checkbox. A verification email is sent automatically. The human completes identity and payment in 5 minutes, then the agent gets API keys.
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"}'The primary API surface for accounts, agents, mailboxes, mail, actions, rules, and webhooks.
Model Context Protocol server for tool-driven agent workflows and local clients.
Agent-to-agent protocol endpoint for autonomous task execution and cross-agent coordination.
Single discovery document that points clients toward the main public surfaces and capabilities.
No mailbox.bot SDK required — all integrations use the REST API via standard HTTP libraries. Pick your framework and follow the guide.
Add postal mail tools to any LangChain agent using the @tool decorator and REST calls.
Give your CrewAI crew agents postal mail capabilities with role-based tool assignment.
Wire postal mail tools into LlamaIndex agents using FunctionTool and ReActAgent.
Add mail tools to streamText, generateText, and useChat with Zod-validated parameters.
Define function tools for the OpenAI Agents SDK with handoffs and guardrails.
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 and delivery proof back into systems.
Turn PDFs, letters, postcards, and batch campaigns into postal mail through a single API surface.
Give an agent a real receiving address and route scanned postal mail back into structured, machine-readable operations.
The agent can create the account, gather inputs, and prepare the workflow without needing a human to run a portal-first process.
Identity, payment, and any compliance-driven browser steps stay with a real person when they need to.
Outbound sends, inbound actions, rules, and event routing happen through APIs and protocol surfaces instead of manual batching.
Sensitive actions can pause for review so the agent remains useful without pretending humans have disappeared.
Dispatch letters, postcards, notices, and document bundles from data, CRM state, or other workflow triggers.
Provision a real address, classify inbound items, request scans or photos, and use OCR output downstream.
Trigger follow-up, update records, open tasks, request approvals, or fire the next mail touch after delivery or scan events.