INBOX-FIRST WORKSPACES FOR AGENTS AND TEAMS

Create inboxes that protect sender reputation from day one.

Dispatch gives you a workspace, inbox-scoped keys, a JSON-first CLI, browser linking, and live mail operations in one flow. We keep every inbox paid because free tiers invite spam, erode trust, and damage deliverability for everyone else.

One operator account One workspace with many inboxes Review every message in the UI Extract codes and links fast

Loading Link Existing Inbox

Private Beta Access

Request access with email, or create an account with an invite code.

Keep onboarding simple: interest list for new users, invite-code signup for approved users.

Join Interest List I Have A Code

Why Dispatch

The part that feels better than stitching five tools together

Inbox-first, not auth-first

The product starts from the resource that matters: create an inbox, select an inbox, inspect mail, send mail.

JSON is the contract

The CLI defaults to machine-readable output so agents and scripts can list mail, extract codes, and send replies without scraping text.

Human handoff in one link

Generate a short-lived inbox link, open it in the browser, and attach the same inbox to a signed-in operator account safely.

Real ops, not a toy inbox

Inbound capture, code extraction, replies, quotas, and scoped keys all work in the same workflow.

How It Works

From first inbox to active mail workflow in four steps

01
Bootstrap a workspace
Create the first inbox with the CLI or bring an existing workspace key back into a fresh machine.
02
Select the inbox that matters now
Workspace scope lets you list inboxes, select one, and mint an inbox key only where you need it.
03
Link the inbox into the browser UI
`dispatch inbox link` hands the selected inbox to a signed-in operator account without widening access.
04
Operate mail from one control plane
Review inbound traffic, extract codes or links, and send replies from Console and Mail Desk.

App Pages

Setup, Console, and Mail Desk

Surface

Setup

Operator sign-in, workspace attach, inbox linking, and active-connection switching live in one place.

Open Setup

Surface

Console

Create inboxes, inspect message history, issue inbox links, and simulate inbound events.

Open Console

Surface

Mail Desk

Review live mail, pull the latest code, and reply from the selected inbox without leaving the queue.

Open Mail Desk

Product loop

Show the full path: workspace setup, inbox receipt, latest-code extraction, and reply sent.

Pricing

Paid access by design to protect trust and deliverability

Inbox Plan

$15

Activate one workspace inbox, then reuse it across sessions with a model built to discourage spam.

Pay with x402 or credit card
Includes 1,000 received + 250 sent
Add 1,000 sent or 1,000 received for $1
No free tier. Paid inboxes keep abuse lower and sender reputation stronger.

Workspace Upgrade

$49

For teams running many inboxes inside one workspace

Attach multiple inboxes to one operator workspace
Manage billing and inboxes from the UI
Built for production inbox workflows and higher-volume teams

Trust

Reputation comes first, not free-volume growth

Sender reputation matters

We optimize for trusted sending behavior, not disposable free inbox volume that trains the system toward spam.

No free tier by choice

Charging from the first inbox filters out low-intent abuse and helps preserve trust for legitimate senders on the platform.

Scoped inbox boundaries

Each inbox keeps its own API key scope so automations and people only touch the mail they should.

FAQ

Fast answers before you launch

Can I start from the CLI before any browser setup?

Yes. Create or reconnect a workspace in the CLI first, then use `dispatch inbox link` to attach the selected inbox to the UI later.

Why does the CLI default to JSON?

Dispatch is built for agents and automations too. JSON-by-default means the CLI is immediately scriptable.

What makes Dispatch feel different?

The inbox is the center of the model, not an afterthought. The same resource flows cleanly from CLI to UI to automation.

Why is there no free tier?

Because free sending surfaces attract spam. Dispatch stays paid from the start to protect sender reputation, delivery quality, and recipient trust.

How is the $15 plan paid?

Either through x402 or standard credit card checkout.

How does pricing help trust?

Requiring paid inboxes raises the cost of abuse and keeps the platform aligned with teams that need reliable, legitimate mail operations.

What is included in the $15 plan?

$15 activates one inbox that you can keep reusing across sessions, scripts, and operator workflows.

What does the $49 plan unlock?

It is for teams that need more inboxes inside one workspace and want billing plus inbox management in the UI.

Create inboxes that protect sender reputation from day one.

Request access with email, or create an account with an invite code.

Current platform volume

The part that feels better than stitching five tools together

Inbox-first, not auth-first

JSON is the contract

Human handoff in one link

Real ops, not a toy inbox

From first inbox to active mail workflow in four steps

Setup, Console, and Mail Desk

Setup

Console

Mail Desk

Show the full path: workspace setup, inbox receipt, latest-code extraction, and reply sent.

Paid access by design to protect trust and deliverability

$15

$49

Reputation comes first, not free-volume growth

Fast answers before you launch

Run inbox operations like a product, not a pile of scripts.