Private beta access
Request access with the workflow you want to run. We review for real agent email use cases: signup codes, receipts, alerts, replies, and human handoff.
Chat and agent handoff
Paste the Dispatch context into ChatGPT, Claude, Codex, or a shell agent. It gets the install path, the current address, mail tailing, code and link extraction, replies, memory, and wallet-backed capacity in one place.
Agent command surface
A person starts in the browser to sign up, pay, and create the first inbox. After that, the CLI is where agents can actually do the work: authenticate, switch inboxes, watch mail, extract artifacts, persist small state, reply, and confirm wallet-funded capacity.
A human can copy a workspace command. A narrow agent can use an inbox key. A wallet-funded inbox can be recovered by signing locally with the funding wallet.
dispatch auth workspace <workspace_key>dispatch auth inbox <inbox_key>dispatch auth wallet --private-key-path ~/.config/dispatch/wallet.keydispatch emaildispatch statusThis is the everyday agent loop: inspect the inbox, wait for mail, pull the useful artifact, and reply when the workflow needs to talk back.
dispatch mail lsdispatch mail taildispatch mail codedispatch mail linkdispatch mail reply latest --text "Thanks, got it."Teams and agents can list addresses, select the active inbox, create more capacity, and claim externally funded inboxes into the account.
dispatch inbox lsdispatch inbox use <inbox_id>dispatch inbox create paid --private-key-path ~/.config/dispatch/wallet.keydispatch inbox claim --openFor lightweight handoffs, an agent can store setup notes, tokens, receipts, or run state under subject keys and retrieve them later.
dispatch memory write agent/setup --stdindispatch memory read agent/setup --rawdispatch memory read session/prefs --wait 30The guide command gives a chat, coding agent, or workflow runner the local command reference it needs to operate the inbox.
dispatch guidedispatch guide --output ./DISPATCH.mddispatch --format json mail codeBilling commands make x402 payment confirmation and entitlement checks scriptable when an agent or builder funds more inbox capacity.
dispatch billing lsdispatch billing confirm x402.<payment_reference> --tx-hash 0xabc123 --chain eth --private-key-path ~/.config/dispatch/wallet.keyIdentity workflow
Start with a paid, claimable address. Wallet proof explains ownership; the inbox is what services and people can actually reach.
dispatch mail codeFinds the latest verification code in the inbox, so an agent can finish signup or login without borrowing your personal email.
dispatch mail tailStreams new messages as they arrive. Use it when a workflow needs to wait for a reply, receipt, notification, or login email.
dispatch memory write <key>Store a small value in the inbox and read it back later from another run. Useful for lightweight state when a workflow spans sessions.
dispatch mail linkExtract magic links, verify-email URLs, receipts, and other links from recent messages.
dispatch inbox create paid --private-key-path ~/.config/dispatch/wallet.keyUse x402 wallet payment from the CLI, or manage Stripe billing from the web app when your team needs more inboxes.
dispatch auth wallet --private-key-path ~/.config/dispatch/wallet.keyThe same wallet that funded an inbox can sign locally later to reopen the workspace. Key material stays on the machine.
dispatch guideWrites a markdown guide with the CLI commands. Add it to your agent context so the workflow knows how to use Dispatch.
dispatch inbox claimAttach an inbox created outside the browser to your Dispatch account, then manage it from Mail Desk and Billing.
Advanced workflow state
For lightweight state, an inbox can store a value under a subject key and read it back later. It is not a database replacement, but it is practical when an agent needs a small piece of context in a later run. The inbox becomes a simple audit trail.
Pricing
Creating live inboxes requires an active entitlement. Use Stripe in Billing or x402 wallet payment from the CLI when you are ready to fund the workspace.
Controlled access helps protect deliverability while we onboard real teams.
Every inbox is tied to a workspace, account, and plan so it is clear who owns it.
Plan limits, inbox count, and entitlements are visible from the Billing page.
Single Inbox
One real address for CLI automation and Mail Desk.
Builder beta
Beta-only deal for up to 500 inboxes on one workspace.
The workspace dashboard
Every inbox in the workspace is visible from the browser. Choose the active inbox, jump into Mail Desk, check billing, and keep developer access close by when the CLI or API is doing the work.
Every inbox on your workspace stays visible in one dashboard, whether it was created in the browser, CLI, or API.
Choose an inbox, jump into Mail Desk, and read, archive, trash, or reply without leaving the workspace.
Manage usage, plans, inbox keys, and developer commands from the same place you inspect mail.
Web path
Private beta can start in the browser or with x402 from the CLI. When a workflow needs a human surface, Mail Desk, Billing, and developer settings stay close to the inbox.
Request access, accept an invite, verify email, and keep the first-run checklist moving.
Request accessRead, search, archive, extract verification codes, and reply from the selected inbox.
Open Mail DeskCheck active entitlements, inbox capacity, Stripe state, and x402-paid workspace status.
Open BillingWhy Dispatch
Most software workflows still borrow a human inbox. That works for demos, but it breaks once agents run independently, pay for resources, and need a durable way to receive messages.
Dispatch gives those workflows dedicated inboxes with wallet claim proof, workspace billing, and a human-readable mail surface. The product is not just an API. It is the identity surface where your team can see what the automation owns, receives, and sends.
The goal is simple: a real address for software, backed by ownership signals teams can inspect.
Shared personal inboxes do not scale, and free throwaway addresses are hard to trust. Dispatch gives every workflow a dedicated address with ownership and usage behind it.
Teams need to know which inboxes exist, when a wallet claim is involved, and what plan backs them. Billing and usage belong next to the mail surface, not in a separate spreadsheet.
Private beta lets us protect reputation while the product grows. The goal is simple: real inboxes that remain useful as more mail is handled by software.
And we're just getting started
Dispatch already gives agents a real inbox they can create, read, and use from the CLI or browser. The next phase is making that same inbox feel bigger: better visibility across teams, tighter CLI-to-browser continuity, and stronger trust signals when autonomous systems operate for real.
Start with a single inbox, then expand into a managed set of addresses for different agents, jobs, and teams.
Create, read, extract, reply, and keep state moving without manual glue every time a workflow spans multiple sessions.
We want better visibility around wallet claims, ownership, inbox health, billing status, and the conditions that make autonomous email usable at scale.
Create or link the inbox so the workflow has its own address.
Operate from Mail Desk and Billing without losing context.
Scale into team workflows with better visibility and trust signals.
Questions
get.dispatchjoin.com/install_dispatch.sh — stable: /bin/bash -c "$(curl -fsSL https://get.dispatchjoin.com/install_dispatch.sh)" — beta channel: DISPATCH_CHANNEL=beta /bin/bash -c "$(curl -fsSL https://get.dispatchjoin.com/install_dispatch.sh)"
Dispatch can use email subjects as lightweight keys. dispatch memory write sends a message to the inbox with the key as the subject and the value as the body. dispatch memory read finds that subject in recent mail and returns it.
Not to join the beta. Billing is managed from the web app when you are ready to add more inboxes or use a paid plan.
Yes. dispatch mail tail polls for new messages and streams them as they arrive. Useful when a workflow needs to wait for a verification email before it can continue.
Yes. Dispatch works from the web app, CLI, or API, so it can sit behind a shell script, Python subprocess, workflow runner, or agent tool call.
Email reputation is shared. Private beta lets us control access, tune deliverability, and work closely with teams using Dispatch in real workflows.
