Head to head · Human approval · October 2026 research run
gotoHuman vs Pushary
Pushary scores 58.5 (C) on agent readiness against gotoHuman's 46.2 (D), and leads in 5 of 7 scored categories. gotoHuman leads on payments & pricing and maintenance & community. Both do human approval.
Best human approval and handoff for AI agents · All 66 human approval comparisons
Which one, for what
Best for A team that wants a ready reviewer inbox where people edit AI output before it ships, without building a UI.
Ahead on
- Payments & pricing, 45 against 15
- Maintenance & community, 77 against 63
Also in its favour
- Runs on your own machine
- No incidents deducted, where Pushary loses 3 points for them
Watch for
No status page, published rate limits or documented error responses
Pushary C
Best for One developer running coding agents unattended who wants questions and approvals on a phone.
Ahead on
- Reliability, 42 against 20
- Schema & documentation, 83 against 49
- Agent ergonomics, 86 against 62
- Security & auth, 66 against 41
- Transparency & trust, 76 against 53
Also in its favour
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
Watch for
No free agent plan, and the 3-day trial needs a card
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Pushary +34
gotoHuman 49
No public OpenAPI for the HTTP API. The 3 MCP tools have typed inputs, but the review data itself is an untyped record (10 of 25). llms.txt and a Markdown copy of every page (10). Tool descriptions say which tool to call first and API pages state purpose, with no guidance on when not to use them (12 of 20). Review data is free-form by design, shaped by the review type you build in the dashboard (7 of 15). SDK, n8n, Make and HTTP examples, but no documented error responses (7 of 15). No API versioning or product changelog. The n8n node keeps a dated CHANGELOG.md on GitHub (3 of 15). Field names still differ across the docs and tools. The API reference and the main request example send data with a required agentId, the assign-reviewers example sends fields with no agentId, and the MCP server links runs with workflow.runId where the API reference documents sessionId. 10+10+12+7+7+3 = 49.
Pushary 83
The hosted server's tool list wasn't read, since nothing is sent to MCP endpoints in this re-check. The tool reference documents each tool's arguments with types and required flags, and the REST API has an OpenAPI 3.1 file linked from llms.txt (15 of 25, the earlier partial kept). llms.txt, Markdown copies of the docs and the skill files are written for agents (10). Per the 1 October reading of the skill, it states when to ask, when to notify and when not to (20). Arguments carry types, ranges such as 1 to 100 for limit, enums such as the flow status, and required flags; question type is an enum of confirm, select and input, and select takes 2 to 6 options (10 of 15). Examples for each tool, and the outcome states (pending, cancelled, expired, missing, unavailable) documented with what to do next (13 of 15). A dated service changelog, versions per component (CLI, Mac app, phone app, SDKs, Hermes plugin) and URL versioning at /api/v1/ with 12 months of security updates for the previous version (15). 15 + 10 + 20 + 10 + 13 + 15 = 83.
Payments & pricing gotoHuman +30
gotoHuman 45
No machine payment protocol (0). Plan prices are public, $0, $79, $350 and Enterprise from $950 a month, with no per-review price (10). Free plan at $0 for 1 user and 300 reviews a month, and the pricing page asks for no card (20). A person signs up in the browser and creates the key (0). 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Pushary 15
No machine payment protocol (0). Public plan prices, Agent at $9.99 a month with 5,000 notifications, Agent Pro $19.99, Team $59 for 5 people and Partner Launch, Growth and Scale at $99, $299 and $799 a month, but no per-call price (10). The pricing page says there is no free agent plan, and the 3-day trial needs a card added to start (0). Setup needs a person to pair a phone and start a paid account (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Security & auth Pushary +25
gotoHuman 41
One workspace API key in an x-api-key header, created in the dashboard, with no scopes found (20). No read-only or scoped keys found, and an autoApprove flag lets the caller skip the human (3 of 20). It returns answers from reviewers you assigned, not third-party content (10). Each result carries the responding user and timestamp. History runs 7 days on Free, 60 on Team and 180 on Business, and audit logs are on Enterprise, from $950 a month (8 of 15). www.gotohuman.com/.well-known/security.txt still answers 404 on 5 November, no disclosure policy or bounty found, and no SOC 2 or ISO 27001 of its own. The home page says all data is encrypted and that 'the core services we use' are certified under SOC 3 and ISO 27001, a claim about its providers' certifications rather than a programme of its own (0 of 20). osv.dev lists no advisory for gotohuman. 20+3+10+8+0 = 41.
Pushary 66
Bearer API keys in the form pk_xxx.sk_xxx, which setup writes after pairing a phone by QR code and fingerprint. The docs describe key kinds with different reach (connector, agent setup and full-access keys, and keys bound to one end user that can only create, read and cancel that user's decisions), but no rotation procedure was found (20 of 30). Enforced gates through Claude Code and Hermes hooks, and propose_scope with allowed and off-limits paths on supported hosts; an agent key can't switch phone approvals off. Plain MCP clients get cooperative questions only (15 of 20). Per the 1 October check, the skill says a text answer containing yes isn't approval for a separate action (12 of 15). The audit trail records each question, the tool, who decided, when and on which surface (12 of 15). SECURITY.md in the skill repository is a disclosure policy with a 48-hour acknowledgement for that repository, and the changelog names an address for vulnerability reports on the service with no stated time. No security.txt (404 on 11 November), bounty or certification of Pushary's own; OSV lists no advisory for pushary (7 of 20). 20 + 15 + 12 + 12 + 7 = 66.
Agent ergonomics Pushary +24
gotoHuman 62
3 compact MCP tools and small JSON responses (25). The query endpoint filters by response and field values and caps at 500 rows, with no cursor (12 of 20). Error responses aren't documented. The SDK throws the status and message and the MCP server returns isError with the text (5 of 20). No idempotency key on review creation, an updateForReviewId in the SDK to revise a request, and no MCP annotations (5 of 20). Three required fields and official SDKs in TypeScript and Python (15). 25+12+5+5+15 = 62.
Pushary 86
The tool reference lists 26 tools, but each key gets a subset. A Claude or ChatGPT connector gets 6, the key setup creates gets 7, and full-access keys add the subscriber, campaign, template and flow tools, with four Partner decision tools on Partner and Enterprise plans. 15 for 11 to 30 tools plus 10 back for per-key toolsets (25). List tools take limit and cursor, flows filter by status, and wait: false and timeoutMs shorten a question (20). Every result carries answered, status and handoffAction, and over-limit errors name the limit (18 of 20). cancel_question, a correlationId and Partner idempotency keys make retries safe, and annotations weren't read (8 of 20). Few required parameters, and official SDKs in TypeScript and Python (15). 25 + 20 + 18 + 8 + 15 = 86.
Transparency & trust Pushary +23
gotoHuman 53
Closed service under German law with clear terms (last updated 13 February 2026), and MIT-licensed SDKs and MCP server (18 of 30). Terms delete customer data within 30 days of termination and rule out training on it, the privacy policy (last updated 13 February 2026) says processing is mainly in the EU or EEA with SCCs for transfers and a data processing agreement on request, and the pricing page sets history at 7, 60 or 180 days or custom. They agree, but no retention period is given for personal data beyond 'as long as necessary' (20 of 30). Terms promise 30 days' notice of material changes, and we found no dated deprecation notices (8 of 20). Processing location stated, processors listed by type with only Stripe named (8 of 20). 18+20+8+8 = 54.
Pushary 76
Closed hosted service under Estonian law with terms updated 1 November 2026, and MIT-licensed skill and adapters (18 of 30). The privacy policy, updated 29 October 2026, says a pending question is cached in Redis for ten minutes or until its deadline, at most 24 hours, that session history is on by default with transcripts redacted and encrypted on the user's machine and recoverable by Pushary compliance admins for legal obligations, that code isn't written to the audit trail, and that the plan's retention window (30 days on Agent to 365 on Team) sets what the dashboard shows while older records aren't deleted automatically. A data processing relationship is described for subscriber data; no DPA document was found (25 of 30). The changelog's deprecation policy says breaking changes are announced at least 90 days in advance, with migration guides (20). Sub-processors are named with what each processes (Clerk, Neon, Vercel, Railway, Redis, Stripe, Resend, PostHog and others) (20). 18 + 25 + 20 + 20 = 83.
Reliability Pushary +22
gotoHuman 20
No public status page found, and the site and docs link none on 5 November (0), so there's no readable incident history (5). No rate limits published for the API (0). No 429 or overload guidance for the API, but webhook deliveries retry up to 7 times with backoff from about 1 minute to 6 hours and carry an Idempotency-Key header (5 of 15, held as a partial). No SLA, and the terms say there are no availability commitments unless an order form adds them (0). The API isn't labelled beta (10). 0+5+0+5+0+10 = 20.
Pushary 42
No public status page found (0) and no incident history (5). The pricing and limits page, read on 11 November, publishes agent limits on every plan (8 pending questions per agent session, 25 per site, 10 notifications per 5 minutes per site) and REST limits per workspace (120 a minute on Agent, 200 on Agent Pro and Team, 60 or 120 a minute for sends) (15). Past a limit the API answers 429 with a Retry-After header and X-RateLimit headers, with guidance to back off exponentially or wait for Retry-After, and Partner decision creates take an idempotency key; ask_user and send_notification, the core writes for the graded plans, take none, though cancel_question and a correlationId make re-asking safe (12). No SLA, and the terms say the service runs "as available" with no guaranteed uptime (0). The hosted server carries no beta label (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.
Score by category
| Category | Weight | gotoHuman | Pushary | Edge |
|---|---|---|---|---|
| Reliability | 16% | 20 | 42 | Pushary +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 49 | 83 | Pushary +34 |
| Agent ergonomics | 13% | 62 | 86 | Pushary +24 |
| Security & auth | 14% | 41 | 66 | Pushary +25 |
| Payments & pricing | 10% | 45 | 15 | gotoHuman +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 63 | gotoHuman +14 |
| Transparency & trust | 7% | 53 | 76 | Pushary +23 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 46.2/100 | C 58.5/100 |
Facts side by side
| Fact | gotoHuman | Pushary |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | gotoHuman | Pushary |
| Hosted endpoint | https://api.gotohuman.com | https://pushary.com/api/mcp/mcp |
| Transports | HTTP, stdio | Streamable HTTP, SSE (legacy) |
| Auth | API key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | MIT (SDKs and MCP server) | MIT (skill, hooks and adapters) |
| Tools exposed | 3 | 26 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Pushary/pushary |
| Last release | 2026-11-04 | 2026-11-04 |
| Terms last updated | no date given | 2026-09-27 |
| Privacy policy last updated | no date given | 2026-09-28 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | 2/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Pushary higher.
| Reviewer | gotoHuman | Pushary |
|---|---|---|
| WardenSecurity auditor | 2/5 An approval gate the agent can switch off | 3/5 Enforced only where the hooks run |
| KeelOperations and maintenance reviewer | 2/5 No changelog, and the docs disagree | 2/5 Weekly syncs, no release notes, no status page |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
gotoHuman
Built for agent review, with TypeScript and Python SDKs, a 3-tool MCP server, an n8n node released seven times since late September and a Make app. No status page, published rate limits or documented error responses, and field names differ across the API reference, guide and MCP server.
Pushary
Pushary's hosted MCP server lets an agent ask a person on their phone and wait for the answer, with 26 documented tools in per-key subsets, published rate limits with Retry-After, and a dated changelog. There's no free agent plan and the trial needs a card, plain MCP clients get cooperative questions only, and there's no status page or SLA.
Before you call either
gotoHuman
- Call
get-form-schemabeforerequest-human-review-with-form, since the field data must match the review type - Send
agentIdand put the review values indataon direct API calls, as the API reference marks both required - Pass a
webhookUrlper request when the review type has no default, or the answer has nowhere to go - Deduplicate webhook calls on the
Idempotency-Keyheader, since delivery is at least once - Set your own deadline on the agent side and treat silence as a rejection
Pushary
- Read
answered,statusandhandoffActionon every result, and never treat a timeout as approval - Expect
ask_userto return at once withanswered: falsewhen the user's mode is notify-only or terminal-only - Poll
wait_for_answeronce, then follow the handoff instead of looping - Cancel a live question with
cancel_questionbefore asking the same thing in chat - Expect 403
subscription_requiredfromsend_notification,ask_userandpropose_scopewhen the workspace has no active plan
Questions
Which is better for AI agents, gotoHuman or Pushary?
Pushary scores 58.5 (C) on agent readiness against gotoHuman's 46.2 (D), and leads in 5 of 7 scored categories. gotoHuman leads on payments & pricing and maintenance & community.
Do gotoHuman and Pushary need an API key?
Both need an API key.
Can an agent call gotoHuman and Pushary without installing anything?
Yes. gotoHuman has a hosted endpoint at https://api.gotohuman.com and Pushary at https://pushary.com/api/mcp/mcp.
Other comparisons with gotoHuman or Pushary
- Agent Inbox vs gotoHuman
- Agent Inbox vs Pushary
- Big Arrow vs gotoHuman
- Big Arrow vs Pushary
- gotoHuman vs Hatchet
- gotoHuman vs Inngest
- gotoHuman vs Orkes Conductor Human tasks
- gotoHuman vs Permit MCP Gateway
- gotoHuman vs Restate
- gotoHuman vs Temporal
- gotoHuman vs Trigger.dev
- gotoHuman vs withHuman
- Hatchet vs Pushary
- Inngest vs Pushary
- Orkes Conductor Human tasks vs Pushary
- Permit MCP Gateway vs Pushary
- Pushary vs Restate
- Pushary vs Temporal
- Pushary vs Trigger.dev
- Pushary vs withHuman
Machine-readable
- This page as Markdown
/compare/gotohuman-vs-pushary.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gotohuman.json·/api/v1/tools/pushary.json - From a terminal
anchor compare gotohuman pushary(the CLI) - Over MCP
compare_tools {"a": "gotohuman", "b": "pushary"}at/mcp, no key