Pricing
Free is live. The rest is being shaped.
RouteToHuman sends your agents’ notifications and approval requests to real people — over email, Slack, and notifications on the web and your phone — and routes the answers back.
Where things stand
Free works today, in full — no credit card, no waiting list, nothing held back for a paid tier it does not have. Solo and Team are on the waitlist while we shape them, so the columns beside Free are a draft of where they are heading, not a price list. Join a waitlist and we’ll tell you the price and the final shape before we ask you for anything.
Compare plans
One plan you can use now, two being shaped.
Scroll sideways to compare plans; feature labels stay in view. With a keyboard, focus the comparison and use the Left and Right arrow keys.
| Feature | Free | Solo | Team |
|---|---|---|---|
| Plans | |||
| Availability | Available now | Waitlist draft — this column may change | Waitlist draft — this column may change |
| Price | $0 | Announced at launch | Announced at launch |
| Messages | |||
| Message types | Notifications | Notifications, acknowledgements, approvals | Notifications, acknowledgements, approvals, choices, guidance |
| Messages / day | 10 | 100 | 10,000 |
| Channels and recipients | |||
| Who can receive | You only | You only | Anyone at your company |
| Your own address | Your own address | Anyone at your company | |
| Slack | Your own DM | Your own DM | Channels and people |
| Web notifications | ✓ | ✓ | ✓ |
| Mobile notifications (iOS, Android) | ✓* | ✓* | ✓* |
| Surfaces | |||
| HTTP API | ✓ | ✓ | ✓ |
| MCP endpoint | ✓ | ✓ | ✓ |
| Web console | ✓ | ✓ | ✓ |
| Command line (rth) preview | ✓ | ✓ | ✓ |
| Webhook | — | — | ✓ |
| Control and visibility | |||
| Registered agents | 1 | 10 | 100 |
| Deliver from your own domain | — | — | ✓ |
| Roles & policy controls | — | — | Per agent, channel, recipient |
| Message history | 7 days | 30 days | 90 days |
| Support | |||
| Support | Community | Priority email | |
* Mobile notifications arrive with the RouteToHuman app for iOS and Android, now in preview; web notifications work today in any browser that supports them.
The plans
Pick one.
The numbers are in the table above; this is the short version and the way in.
Solo
For personal agents that need to ask you to decide, not only to tell you.
Draft — shape and price are not settled.
Team
For agents that need to reach the people around you, from your own domain.
Draft — shape and price are not settled.
Details
What is a registered agent?
An agent is a named sender you register with RouteToHuman. Each one gets its own credential, and its name is what your recipients see — so a message reads as from your deploy bot, not from an anonymous API key. It does not have to be intelligent: a scheduled job or a CI pipeline that sends we are starting and we are done is an agent too, and counts as one.
Registering agents separately means you can revoke one without disturbing the others, see usage broken out per agent, and — when Team ships — set different permissions for each: which people it may reach, over which channels, with which message types.
How limits work
One number per plan: messages a day. Email, Slack, and notifications all count against the same allowance, and it resets at midnight UTC. There is no monthly total to plan around, no extra plan-specific burst quota, and no separate approval allowance for plans that support approvals.
API safety limits still apply. The messages API allows 60 requests a minute, including reads; the email API allows 30 requests a minute. These limits are separate from your daily message allowance. A rate-limited request returns HTTP 429 with a Retry-After header: wait that long before trying again.
When you hit the limit, we stop sending. Your agent gets a clear, specific error — not a silent drop and not a surprise bill. We notify you as you approach the limit (through RouteToHuman, naturally), and the count starts over the next day.
A message is one person asked once. Reaching three people costs three, however you send them. Reaching one person costs one even when we try more than one way — if a browser notification goes unanswered and we follow up by email, that escalation is still a single message against your day.
Channels on the back burner
SMS, voice, Microsoft Teams, WhatsApp, Telegram, and Discord are not available yet on any plan. If one of them is the channel your people actually live in, tell us which and we’ll tell you when.
Who can receive messages
On Free and Solo: you. Your agents’ email goes to your own address, from our sending domain, and nowhere else.
On Team: the people at your company. You confirm each company domain once in RouteToHuman, and your agents can then reach anyone on it. Anyone outside it stays unreachable — which is what keeps your messages out of spam folders, and other customers’ agents away from your people.
Questions
What do I get on Free, exactly?
Ten messages a day to yourself, over email or your own Slack DM, plus web and mobile notifications — sent from an agent, a scheduled job, a CI pipeline, or your own terminal, through the HTTP API, the MCP endpoint, the command line, or the web console.
Why are Solo and Team on the waitlist?
Their feature sets are still being shaped, and we would rather publish a price we intend to keep than one we withdraw. The columns beside Free are a draft of where each is heading.
Will Free stay free?
Yes. Free is the whole product at its own scale — every surface, no crippled API — and it is what we support today.
Do I need a credit card for Free?
No.
More questions? Write to hello@routetohuman.com.