Community
$0 / month
500 resolutions / month
- 3 days of history
- 2 notification devices
- 5 pending requests or tasks
Human input
for your agents.
Send approvals, forms, and files. Get structured responses back. Declare the tasks your agents accept, and send work the other way.
ONE SYNCHRONIZED INBOX
Every machine.
All together.
Requests from your laptop, servers, and cloud agents arrive in one activity list. Respond from any device, with forms, tables, code, and files kept together with each message.
HOW IT WORKS
Many connections.
One private inbox.
Your agents connect to Herald. Requests reach your apps, and responses return to the connection that asked. All content is end-to-end encrypted, and your runners keep control of execution.
- Sealed at the sourceMessages, answers, files and task inputs, logs and results are encrypted on the device or connection that writes them.
- Herald relays ciphertextThe server stores and routes what it cannot read, and refuses anything unencrypted.
- Opened only by youOnly your devices and the connection a message is addressed to can decrypt it. Every device shows the same safety code.
PRICING
Start with 500
free resolutions.
An answered request, a delivered one-way update, or a runner-acknowledged task each counts as one resolution. Prices are in USD.
Starter
$9 / month
10,000 resolutions / month
- 90 days of history
- 10 notification devices
- Lock-screen actions and signed webhooks
- More resolutions: $5 per 10,000
Pro
$18 / month
40,000 resolutions / month
- 90 days of history
- 10 notification devices
- Lock-screen actions and signed webhooks
- More resolutions: $5 per 10,000
Team
Send requests to a team, not a person.
Herald picks who answers, records who did, and escalates when nobody does. Every member gets everything in the personal plans.
Request Access- Team inboxesAgents address a team, not one person. Members see what is open, who has it and who answered.
- Round robin or first responderRotate requests across members, or notify everyone and take the first answer.
- Tiered escalationUnanswered after a set time, a request moves to the next person or tier.
- Seats for people onlyResolutions pool across seats. Agents, connections and runners never take one.
QUESTIONS & ANSWERS
Before you connect.
What happens if my agent disconnects while waiting?
The request and its response remain available until their history expires. Your agent can reconnect and retrieve the answer using the message ID; it does not need to keep a connection open while you decide.
What happens if I miss a request’s deadline?
An expired request can no longer be answered. A timeout in the CLI only stops that wait; it does not cancel the request. The request stays open until its deadline.
Can a runner on my laptop receive work without a public URL?
Yes. The CLI runner makes outbound connections to Herald to pick up work. It does not require an incoming port or a public server address.
Can one connection read another connection’s messages?
Connections use scoped credentials. A connection can access its own messages and replies, plus thread context explicitly assigned to its tasks. Connecting an agent does not give it access to your entire inbox.
Can Herald read my messages?
No. Content is encrypted on the device or connection that writes it, and only your devices and the connection it is addressed to can decrypt it. Herald sees metadata such as senders, times and status, and refuses anything unencrypted.
How should I send passwords or API keys?
Use a secret field instead of an ordinary message or attachment. Secret responses are encrypted to the requester and excluded from message history and notifications. Messages and files are end-to-end encrypted too, but they stay in your history.
Can several people share one inbox?
Not yet. Herald accounts are personal: one account is for one person. A Team plan with round robin, first responder and escalation is in development; request access to it from the Team tab under pricing.