HITL vs Permit.io
HITL reaches the right person with nothing to embed: ask any question, not only for access, and build multi-stage approvals that branch on every answer.
TL;DR: three reasons teams pick HITL
HITL keeps a person in the loop on AI agents, from a one-tap approval to a multi-stage review that branches on every answer. Here is where it pulls ahead of Permit.io.
Branching workflows: route by category, branch on the answer and chain reviews for multi-stage sign-off.
Nothing to build: requests go to ready-made apps on iPhone, Apple Watch, Android and the web, and to Telegram.
Ask for more than access: choices, text, an editable draft, a number or a rating, with a default answer on timeout.
Built for complex decisions, not just yes or no
In HITL a workflow is a graph, not a straight line. Classify the request, ask the right person, branch on what they say and merge back. Build it on a canvas, or describe it and let the workflow assistant build it for you.
Yes: Send the refund · No: Email the customer
As many reviews as the decision needs
Put several Human Review steps in one workflow: a first check, a second sign-off, an escalation, and a different reviewer on each branch.
Branch on the answer
A Condition step routes on what the person decided or on the data. An AI Classifier sends each request down the path for its category.
Paths that meet again
Branches can merge back into one path, so a refund, an escalation and a drafted reply can all finish with the same follow-up step.
Describe it, get the workflow
The built-in workflow assistant builds the graph from a plain-language prompt. Every revision is kept, so you can restore an earlier one.
Nine step types on the canvas
- TriggerStart on a schedule, an email or a spreadsheet row.
- Human ReviewAsk a person to decide, with any of the 7 response types.
- AIRun a prompt on the data so far.
- AI ClassifierSort input into categories, each with its own path, plus Other.
- ConditionBranch yes or no on the answer or on any data.
- TransformSet variables for the steps that follow.
- DataFetch from Google Sheets, an API or a table.
- ActionCall a webhook, send an email or post to Slack.
- EndClose the run once every path is done.
What about Permit.io?
Permit.io's Access Request MCP docs cover asking for access to a resource and one-time approval of an operation, approved or denied through Elements or the API. We could not find a branching review workflow. HITL adds one around any question.
Feature comparison
Where HITL leads comes first. Then the features HITL and Permit.io share, from connecting agents to pricing.
| Feature | HITL | Permit.io |
|---|---|---|
| Nonlinear workflows (branching, multi-step review) | YesBranches, AI routing, several review steps | Not listed |
| Visual workflow editor | YesCanvas with 9 step types | Not listed |
| Callback webhooks | YesPer request | Not listed |
| Answers beyond approve or deny | Yes7 response types | Not listedApprove or deny |
| Timeouts with a default answer | Yes | Not listed |
| iPhone app | Yes | Not listed |
| Apple Watch | Yes | Not listed |
| Android app | Yes | Not listed |
| Telegram | Yes | Not listed |
| MCP server for agents | YesHosted, with sign-in | YesOpen source server |
| REST API | Yes | Yes |
| Web inbox | Yesmy.hitl.sh | YesEmbeddable Elements |
| Free plan | Yes500 requests / mo | Yes1,000 MAU |
| Slack | Coming soon | Not listed |
"Not listed" means we could not find it on Permit.io's public site or docs in October 2026. It may still exist. "Coming soon" channels are on HITL's roadmap and not live yet.
The products, side by side
HITL's web inbox next to a product image Permit.io shows on its own site.
HITL web inboxfrom hitl.sh
Permit.iofrom permit.ioAbout Permit.io
Permit.io is an authorization platform for RBAC, ABAC and ReBAC. Its open source Access Request MCP server lets an agent ask for a role on a resource or for one-time approval of an operation. People approve through Permit's embeddable Elements, the Permit API or tools the agent calls.
Why teams pick HITL
For the people who answer the requests and the teams who run the workflows.
Approvers do not need your app
Reviewers install HITL on their phone or open the web inbox. You do not have to embed an approval screen in your own product first.
Any question, not only access
Use HITL to approve a refund, pick a reply, fix a draft or score an output. Access requests are just one kind of question.
Workflows and no-code
Chain Human Review steps and branch on each answer in the workflow editor, or call HITL from n8n, Zapier and Make.
Helps with oversight rules
Each answer is recorded with who gave it, which helps with the human oversight Article 14 of the EU AI Act asks for.
Why agents work well with HITL
For the agents asking the questions. HITL gives them a clear contract: ask, wait, get a typed answer.
A hosted MCP server
Add https://mcp.hitl.sh/mcp to Claude Code, Cursor or any client that supports remote MCP. Sign in once and the agent gets tools like list_loops, create_request and get_request.
A structured answer, every time
The agent picks one of 7 response types and gets back typed data: a decision, the chosen options, a number, a rating or the edited text. No parsing a chat reply.
Timeouts that keep work moving
Every request carries a default response. If nobody answers in time, the agent gets that answer and carries on instead of waiting forever.
A setup prompt the agent follows
Copy the setup prompt from hitl.sh and paste it into your agent. It asks for your API key, reads the docs at docs.hitl.sh/llms.txt and lists your loops to prove the connection works.
Add HITL to Claude Code
claude mcp add --transport http hitl https://mcp.hitl.sh/mcpQuestions
What teams ask when they weigh HITL against Permit.io.
- Why choose HITL over Permit.io for agent approvals?
- HITL sends any question to a person on ready-made apps and returns a structured answer, with 7 response types, timeouts and branching workflows. There is nothing to embed in your own product first.
- Where do people approve requests in Permit.io?
- Through Permit Elements, embeddable components you place in your own app, or through the Permit API. HITL sends requests to its own apps and to Telegram, so reviewers can answer today.
- Can HITL run multi-stage approvals?
- Yes. Add several Human Review steps to a workflow, branch on each answer and give each branch its own reviewers.
- Can I use Permit.io and HITL together?
- Yes. Permit.io can decide who is allowed to do what, and HITL can ask the right person when an agent needs a decision or an answer.
- How does pricing compare?
- HITL is free for 500 requests a month, then $10 or $30 a month. Permit.io has a free Community plan with 1,000 monthly active users, and paid Pro and Enterprise plans.
Sources
Facts about Permit.io come from these public pages, checked in October 2026. Products change, so check them for the latest. Spot something out of date? Email [email protected].
Ship AI workflows your team can trust
Free to start. Your first workflow takes minutes.