Inboxes on demand
Create, list, send, reply, threads. IMAP for mail clients is agent.voru.org port 1993.
One API call mints an inbox. Webhooks fire when a human replies. Built for products that provision a mailbox per tenant — not for cheap bulk send.
No credit card
from agentbox import AgentBox
client = AgentBox("ab_live_...", base_url="https://voru.org")
inbox = client.inboxes.create(username="billing")
client.inboxes.send(
inbox["inbox_id"],
to="ops@acme.com",
subject="Workspace ready",
text="Reply in this thread.",
)live-box@agent.voru.orgA live address on agent.voru.org. Stalwart on this server is the mail stack.
Create two inboxes and send between them — that is the production path.
POST /v1/inboxes
GET /v1/inboxes/{id}
client_id makes create idempotent.
metadata is yours to store.Browser agents, assistants, document intake, support routing — each one gets its own mailbox.
live-box@agent.voru.org
847293
cURL against https://voru.org/v1. Python and TypeScript clients live in the repo — they are not on PyPI or npm.
# SDK is in the repo, not on PyPI/npm # pip install -e packages/sdk-python curl https://voru.org/v1/openapi.json
An inbox API. You create an address per customer or agent, then send, receive, and subscribe to events.
SaaS teams who want one mailbox per customer or agent — create, watch, and delete it from the API.
Create, list, send, reply, threads. IMAP for mail clients is agent.voru.org port 1993.
message.received, sent, bounced. HMAC signed. Or listen on the WebSocket at /v1/ws.
One pod per customer in your product. Map with client_id so you do not store our IDs.
SPF, DKIM, DMARC generated. Unverified domains cannot send. Free tier stays on ours, on purpose.
Custom domain, a third inbox, or sending past the allowlist — any of those is the upgrade. $12 and $39 sit under the usual developer / startup jump.
Try the API on our domain.
The first real product plan.
One box per customer.