About Herald by Wusulab
Publishing is now a job people share with software.
AI agents can write a week of posts in a minute. What they cannot do is decide what your brand should say. Most scheduling tools were built for one person at one keyboard, so teams paste agent output into them by hand, or let agents post with nobody looking.
Herald is built for the way the work is really split: agents draft, people decide, and the system publishes and remembers. It is a scheduling tool first, with approvals, roles and an activity log designed in from the start.
- social networks, plus email
- 9social networks, plus email
- tools agents can call over MCP
- 58tools agents can call over MCP
- roles, set per workspace
- 4roles, set per workspace
- activity log that records everyone
- 1activity log that records everyone
What Herald believes
An agent can write the post. A person decides that it goes out.
- A person answers for every post
- Agents can do most of the work. Someone on your team still decides what carries your name, and Herald makes that decision quick.
- Permissions are specific
- An agent that writes captions does not need to delete channels. Every key carries exactly the actions, channels and approval rule you give it.
- The record is part of the product
- Who wrote it, who approved it, when it went out and what changed. Not a report you request: it is there on every post.
- Your content stays yours
- Herald stores what it needs to publish for you, uses it for nothing else, and deletes it when you ask.
How Herald is built
Four parts, each with one job. Every request, from a person or an agent, goes through the same API and the same permission checks, and every action is written to the log.
Web app
Where your team writes, reviews, plans and keeps media.
API
One door for the web app, your scripts and your agents, with the same permission checks for all of them.
Worker
Publishes on schedule, retries when a network is briefly down, renews channel access and sends notifications.
MCP server
Lets Claude and other MCP clients use Herald as a tool, under the agent's own key.
Data lives in PostgreSQL, media in Cloudflare R2 with checksum verification, and publishing goes through each network's official API.
Who Herald is for
Small teams and creators
One calendar for every network, with drafts you can hand to an agent and check before they go out.
Agencies
A workspace per client, roles per workspace, and one view across all of them.
Teams building with agents
A publishing tool your agents can call safely, with approvals and a log you can show a client.
Talk to us
Questions, feedback, or a request to delete your data: write to us and a person will answer.
Herald by Wusulab is built and operated by Wusulab.