Dispatch · One address that runs any action
One web address runs any action in the Directory.
A person, a program, an AI model, a spreadsheet cell or an iPhone Shortcut sends dispatch the name of an action and its inputs. Dispatch looks the action up in the Directory, checks the permissions, runs it on the right computer, sends back the result and stores an entry in the Ledger.
A text
Sent from your number
A link
Figure written into the cell
A spreadsheet cell
Uploaded, paused
An iPhone Shortcut
Opened, locked again at 10:15
A typed command
Phone on, app open
An AI model’s tool call
Refused: no permission covers this
- looks up the action
- checks permissions
- sends it to a computer
“Text back the 2:18 missed call”, sent as a text.
An illustration, running in your browser; the business is made up. The entry fingerprints are real SHA-256 hashes, computed in your browser.
Dispatch is a single web address. You, your staff, a spreadsheet, an iPhone Shortcut or an AI model send it the name of an action and its inputs. It finds the action in the Directory, checks your permissions, runs it on the right computer, sends back the result, and writes an entry in the Ledger.
Because every request goes through the same address, the same permissions apply whether a request comes from a text message, a link, a spreadsheet cell, a Shortcut, the command line or an AI model, and every request is recorded the same way. One action can be switched off in one place.
Every action is invoked as an HTTP POST of {"key": "<action name>", "args": {…}}. REST, MCP, spreadsheet formulas, text tags and webhooks are different ways of making that same request. Actions run on Cloudflare servers, a Mac, an iPhone, a browser, a virtual machine or a phone.
Live, read from this site at 11:06 AM.
For your business
What one address does for a business
Without dispatch, every tool your business uses needs its own connection to every service it touches, each with its own login, its own permissions and its own record. With dispatch, every tool sends its requests to one address. Here is what that changes for a business, in five points, each with an example.
One connection per tool, instead of one for every tool and every service.
Each outside service, such as Messages, Google Calendar or Meta ads, is connected to the system once, as actions in the Directory. Each tool your business uses, such as a spreadsheet, the AI assistant or an iPhone Shortcut, connects once, to dispatch. After that, every tool can run every action: 1,335 of them in this system today.
Example: three tools and three services
Without dispatch9 connections
- Your spreadsheet
- The AI assistant
- An iPhone Shortcut
- Messages
- Google Calendar
- Meta ads
With dispatch6 connections
- Your spreadsheet
- The AI assistant
- An iPhone Shortcut
- Messages
- Google Calendar
- Meta ads
Add a fourth tool and a fourth service: 16 connections without dispatch, 8 with it. Each connection is a login to keep working, and a place where something can break.
Your staff, your AI models and your phone use the same actions, with the same permissions.
The action “Send a text from your number” exists once. Whoever sends the request, it sends from the same number, under the same limits, and is stored in the Ledger the same way.
Example: one action, used three ways in one day
all three run
An illustration. The business and the people are made up.
Switching to a different AI model does not mean rebuilding anything.
The actions, their limits and the Ledger belong to the Directory and to dispatch, not to the AI model. If the AI assistant on your number runs on Claude today and you want to try Gemini, you change which model it uses. It sees the same actions with the same limits, and both models’ work sits in the same Ledger, so you can compare them.
Example: pick a model; the actions do not change
- Actions the assistant can runlimit
- Send a text from your numberapproved prices only
- Book into open hoursonly hours you opened
- Refund to the original cardup to $500
Model: Claude. Changed: one setting. Rebuilt: nothing.
One place to switch an action off, for every tool at once.
Every request passes through dispatch, so an action switched off there is refused whichever tool asks for it. There is no list of tools to go through one by one, and each refused request is stored in the Ledger.
Example: stop new Meta ads tonight
- Your staff’s spreadsheetruns
- The AI assistantruns
- A script your developer wroteruns
- A saved linkruns
Tap the switch. An illustration, running in your browser.
Every action is recorded the same way, whoever asked for it.
A text sent by a person tapping a Shortcut at noon and a text sent by an AI model at 2 AM produce Ledger entries with the same fields. So one search answers “what did we send this customer, and who sent it?” across every tool.
Example: two entries for the same action
- When
- 12:04 PM
- Sent by
- You, from an iPhone Shortcut
- Action
- Send a text from your number
- Input
- “On my way, about 20 minutes.”
- Result
- delivered 12:04 PM
- Fingerprint
- 9d68b165665aa056…
- When
- 2:13 AM
- Sent by
- The AI assistant (Claude)
- Action
- Send a text from your number
- Input
- “Yes, Thursday 8 to 10 is open.”
- Result
- delivered 2:13 AM
- Fingerprint
- afab6e2a4e0a9b94…
An illustration. The fingerprints are real SHA-256 hashes, computed in your browser.
Try it
Change how a request is sent; every step after dispatch stays the same.
Pick how the request is sent and what it asks for. The action, its permissions, the computer that runs it and the Ledger entry are the same whichever way the request arrives. Change only the way it is sent and watch the steps marked “same as before”.
1How it is sent
2What it asks for
1 · Request arrives
2 · Action looked upsame as before
3 · Permissions checkedsame as before
4 · Computer runs itsame as before
5 · Ledger entry storedsame as before
An illustration, running in your browser; the business is made up. Each entry’s fingerprint is a real SHA-256 hash, computed in your browser from the entry and the fingerprint of the entry before it.
Ways in, computers out
Many ways to send a request, several kinds of computer, one address between them.
One list shows the ways a request can arrive; the other shows the computers that carry out actions. Dispatch sits between them, so adding a new way to send requests, or a new computer, does not require a new system.
Ways to send a request
Each one is turned into the same two things: the name of an action, and its inputs.
- A textFrom your phone to your own business line.
- A linkOpening the link runs the action.
- A spreadsheet cellType the request; the answer appears in the next cell.
- An iPhone ShortcutA tap, or an automatic trigger on the phone.
- A typed commandOne line typed in a terminal (the text window developers use).
- An AI model’s tool callClaude, ChatGPT, Grok, Gemini or any AI model that can call tools.
- A webhookAnother program sends a message to a web address when something happens.
The computers that run actions
Each action runs on one of these. Counts are read from this system’s Directory just now.
- Cloud serversRun actions while your own computers are off.28 actions
- Your MacFor actions that need the Mac’s screen, apps or files.118 actions
- Your iPhoneThrough Apple Shortcuts: apps, the camera and the share menu.23 actions
- A browser signed in as youChrome or Safari, signed in to your own accounts.41 actions
- Rented Android phonesIn a data centre, for apps that only work on a phone.4 actions
- Recorded stepsA website with no connection for programs, recorded once. See below.19 actions
However a request arrives, dispatch turns it into the same two things: which action to run, and with what inputs. It sends the action to the computer that runs it, and sends the result back the way the request came.
Because every request goes through the same address, the same permissions apply whether a request comes from a text message, a link, a spreadsheet cell, a Shortcut, the command line or an AI model, and every request is recorded the same way. One action can be switched off in one place. Depending on the action, the work happens on Cloudflare’s servers (always on), on your Mac, on your iPhone, in a web browser signed in to your accounts, or on Android phones rented in a data centre for apps that only run on a phone.
Every action is invoked as an HTTP POST of {"key": "<action name>", "args": {…}}. REST, MCP, spreadsheet formulas, text tags and webhooks are different ways of making that same request. Actions run on Cloudflare servers, a Mac, an iPhone, a browser, a virtual machine or a phone. Executors: Cloudflare Workers and containers, a Mac bridge program, iPhone Shortcuts and App Intents, persistent browser profiles, cloud Android phones and Mac virtual machines. Recording steps and compiling them turns any website into a Directory row callable through dispatch.
Websites with no API
A website with no API can be recorded once and become an action.
Some websites, such as a supplier’s stock page, have no API (no way for another program to connect to them). The steps are done once in a browser signed in as you, and recorded. The recording becomes a new action in the Directory, which can then be run every way any other action can.
Northside Supply · Stock
Signed in as you. No API and no export button.
- 1Open the stock page, signed in as you
- 2Find the part
- 3Read the number in stock
Saved as a new action
- Runs on
- A browser signed in as you
- Its limit
- read only, this one website
- Ways to run it
- 26, like every action
Record the steps
Do the task once in a browser signed in as you. Each step is saved, with a screenshot.
It becomes an action
The recorded steps are saved as a new row in the Directory, with a name, a limit and every way to run it.
Run it whenever you need it
By text, from a spreadsheet cell, or from an AI model. For example: “Check the supplier’s stock page every morning and text me only when it changes.”
An illustration. The supplier, the website and the stock are made up.
Use it yourself
Send requests to dispatch from your own tools
You, your staff and your developers can run actions directly: from your own software, an AI app, a terminal, a spreadsheet, a Shortcut or another program. Each page below explains one way to connect and what you need for it.
Every request, whichever way it arrives, is checked against your permissions and stored in your Ledger, exactly like the requests your staff and your AI assistant send.
ways to send a request for each of the 1,335 actions in this system’s Directory, all through one dispatch address.
Live, read from this site at 11:06 AM.
Every way, explained on the Directory pageText me.
Tell me one thing you would like to be able to ask for by text. I’ll tell you which action in the Directory would run it, and what its limit would be.