Get verification codes
dispatch mail otpLooks at your bot's recent emails and pulls out the auth code. Works on anything — Stripe, GitHub, whatever sent it.
01
What it can do
The commands agents run independently.
Works with any AI agent, automation script, or bot framework.
Watch mail come in
dispatch mail tailStreams new messages as they arrive. Good for when your bot needs to wait for a reply or a notification before it can move on.
Remember things
dispatch memory write <key>Your bot can store a value and read it back later, even in a different session. Useful for tokens, preferences, anything it shouldn't have to re-fetch.
Pull links from emails
dispatch mail extract --kind linkSame idea as the OTP command, but for magic login links and verify-email URLs. Your bot clicks the link so you don't have to.
Pay with a crypto wallet
dispatch inbox create --private-key 0x…Pass a wallet key and Dispatch charges it directly. No checkout page, no card. Works with Ethereum or Solana.
Log in once
dispatch auth workspace ws.secretSave your workspace key locally. After that every command just works — you won't be prompted again.
Drop a cheat sheet into context
dispatch guideWrites a markdown file with the full command reference. Drop it into your AI's context at the start of a session and it'll know what to do.
Connect it to your account
dispatch inbox claimAn inbox your bot created can be linked to your account so you can browse it from the web. Handy if you want to keep an eye on what it's receiving.
02
More than just email
Agents remember things
between sessions.
It works by emailing itself. Write a value under a key, and it shows up as a message in the inbox. Read it back anytime, from any session. No database, no extra service to set up. The inbox is the store.
Pricing
$15 to get started.
One-time payment. No subscription, no monthly bill. We charge upfront because agent reputation will be economic before it is social. Cost will not solve trust by itself, but it is the clearest signal that still holds when software can create inboxes endlessly.
Serious senders only
Private-beta access keeps spammers out and makes the whole network more trustworthy.
Better deliverability
Access is invite-gated during the beta, so your emails do not share a reputation with open signups.
Pay once, done
No renewal dates, no cancellation flows. It keeps working until you run out of events.
Lifetime Inbox Bundle
$15
One-time. One inbox. One workspace.
- 10,000 lifetime events + 2 GB permanent storage
- Rate limits: 3/min · 30/hr · 120/day
- Top-ups: +10k events = $6 · +5 GB = $10
- Pay from CLI with a crypto wallet — no card needed
Multi-Inbox Workspace
$49
Required before adding a second inbox.
- Unlocks multiple inboxes on one workspace
- One control plane for billing and inboxes
- Right size for a small team after single-inbox validation
Live usage
Inboxes created
49
Emails processed
32
Human operators linked
19
The control panel
See every agent inbox you control.
After an agent claims an inbox, it appears in the control panel. That gives you one browser surface where you can scan every linked inbox, choose the active one, and jump straight into Mail Desk to read all of that agent's email.
See every linked inbox
Once an agent claims an inbox, the control panel keeps it in one registry tied to your operator account.
Open that inbox's email
Pick an inbox, jump into Mail Desk, and read the full message history for that specific agent.
Operate from one place
Refresh inboxes, check activity, rotate keys, and manage credits without bouncing between tools.
The web interface
Setup, Control Panel, and Mail Desk.
Claim inboxes in Setup, see every linked agent inbox in the Control Panel, then open Mail Desk to browse that inbox's email, extract codes, and reply from the browser.
Setup
Sign up with an invite code, verify your email, and claim your first inbox.
Open SetupControl Panelprimary
See every inbox your agents own, switch the active one, check activity, rotate keys, and manage credits in one place.
Open Control PanelMail Desk
Browse the selected inbox's email, pull out verification codes, search messages, and reply inline.
Open Mail DeskWhy Dispatch
Agent reputation will be economic before it is social.
For years, email trust was built around human behavior: signups, friction, and long-lived accounts. Agents change the shape of the problem. They can create identities quickly, operate continuously, and retry forever. That means a lot of the old anti-spam assumptions stop carrying real weight.
The near-term signal that still matters is cost. If an inbox is paid for, kept alive, and expensive to abuse, it is easier to trust than a free throwaway identity. Dispatch is built around that reality: real inboxes for autonomous systems, backed by a trust model that survives automation.
Payment is not the whole reputation system. It is the first trust signal that does not disappear the moment agents can move faster than humans.
Human trust patterns do not transfer cleanly
Old anti-spam systems assume a person behind the address: slow signup, manual friction, and identities that are expensive to rotate. Agents break that assumption.
Cost becomes the cleanest early trust signal
When software can generate inboxes at machine speed, free identity stops meaning much. Payment is not the whole reputation system, but it is a signal abuse cannot fake cheaply.
Dispatch makes that signal legible
We want agent inboxes to be real, funded, and accountable. That is how you keep deliverability usable as more email gets generated by software instead of humans.
And we're just getting started
The inbox is becoming an operator surface, not just a mailbox.
Dispatch already gives agents a real inbox they can provision, claim, read, and use as memory. The next phase is making that same inbox feel bigger: more visibility across fleets, tighter CLI-to-browser continuity, and better trust signals when autonomous systems operate for real.
CLI-first foreverInbox fleetsMail Desk workflowsTrust-aware identity
Current thesisPaid, programmable inboxes give autonomous systems a real identity surface. The rest of the product grows out from that.
From one inbox to fleets
Dispatch already works for a single agent inbox. The next layer is better visibility once an operator is managing a whole cluster of them.
Longer-running agent loops
Provision, claim, extract, reply, and keep state moving without falling back to manual glue every time a workflow spans multiple sessions.
Sharper trust surfaces
We want more operator-readable signal around funded identities, inbox health, and the conditions that make autonomous email usable at scale.
Signal pathCLI → web → scale
01
Create or claim the inbox so the agent has a funded identity.
02
Operate from Mail Desk and the control panel without losing context.
03
Scale into multi-agent workflows with better visibility and trust signals.
Questions
The ones we get every time.
Where do I install from?
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)"
How does the memory system work?
Your bot emails itself. dispatch memory write sends a message to the inbox with your key as the subject and the value as the body. dispatch memory read looks for that subject in recent mail and returns it. No extra services needed.
Do I need a credit card?
Not for signup. Dispatch supports wallet-based x402 and card-based billing for paid features when those flows are enabled.
Can my bot watch for emails in real time?
Yes. dispatch mail tail polls for new messages and streams them as they arrive. Useful when your bot needs to wait for a verification email before it can continue.
Does this work with any AI agent or bot framework?
Yes — it's just a CLI tool. Run it from a shell script, a Python subprocess, an n8n node, a Claude tool call, whatever. Run dispatch guide to get a markdown reference your AI can read at the start of a session.
Why private beta?
Email reputation is shared. A private beta lets us keep access controlled, tune deliverability, and avoid pretending signup payment is enforced when it is not.