Head to head · Human approval · October 2026 research run

gotoHuman vs Orkes Conductor Human tasks

Orkes Conductor Human tasks scores 55.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 transparency & trust. Both do human approval.

Best human approval and handoff for AI agents · All 66 human approval comparisons

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Which one, for what

gotoHuman D

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 30
  • Transparency & trust, 53 against 46

Watch for

No status page, published rate limits or documented error responses

Orkes Conductor Human tasks C

Best for Teams that already orchestrate agents as Conductor workflows and need formal routing, per-assignee deadlines and escalation without writing them.

Ahead on

  • Reliability, 32 against 20
  • Schema & documentation, 65 against 49
  • Agent ergonomics, 69 against 62
  • Security & auth, 77 against 41

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow

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.

Security & auth Orkes Conductor Human tasks +36

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.

Orkes Conductor Human tasks 77

Application access keys with roles and per-resource read and execute permissions, swapped for a JWT at /api/token. The JWT expiry is configurable, and a negative value means it never expires (25 of 30). RBAC, application roles, assignment to named users or groups, and a TERMINATE strategy that fails the workflow when nobody answers (18 of 20). It returns form answers from assigned reviewers (10). Human task states and history are kept per task, and the Audit Logs page (in the docs repository since 12 August 2026, v5.5.0 and later) records who created, updated or deleted 21 resource types, HUMAN_TASK and ACCESS_KEY among them. It's off by default, switched on through Orkes support, visible to administrators only and doesn't cover task runs (12 of 15). Conductor OSS's SECURITY.md routes reports through GitHub's private advisory form, with no acknowledgement time (7), and the pricing page names SOC 2 Type II for Enterprise per the 1 October check. No bounty found and security.txt unread (12 of 20). 25 + 18 + 10 + 12 + 12 = 77.

Schema & documentation Orkes Conductor Human tasks +16

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.

Orkes Conductor Human tasks 65

No public OpenAPI found for the Orkes API. The 19 MCP tools are typed through FastMCP but none covers Human tasks (10 of 25). llms.txt exists but is the whole documentation in one 2.57 MB file with no index, which an agent can't use as a map, so 7 of 10. Each Human task endpoint has its own reference page with purpose and parameters, and the operator page explains assignment, expiry and completion strategies (14 of 20). Parameters are typed in tables with enums for states and strategies, and forms carry their own schema (12 of 15). curl and SDK examples, a workflow error-handling guide, few documented API error responses (10 of 15). Conductor OSS releases on GitHub and a product changelog page (12 of 15). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. The docs repository's static/llms.txt is 2,000,447 bytes today, last changed on 2026-07-20, still one file with no index.

Payments & pricing gotoHuman +15

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.

Orkes Conductor Human tasks 30

No machine payment protocol (0). Paid editions are contact sales only (0). The hosted Developer Edition is free, with no card mentioned, though the pricing page says it isn't for production (20). A person signs up in the browser and creates an application key (0). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Orkes Conductor Human tasks +12

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.

Orkes Conductor Human tasks 32

No public status page found for Orkes Cloud or the Developer Edition, in a web search or the docs repository on 4 November (0), so no readable incident history (5). API rate limits aren't published. The rate-limit page covers per-task execution limits you set yourself, and the Developer Edition says its limits may change (0). No 429 or backoff guidance found, but workflow starts take an idempotency key with FAIL, RETURN_EXISTING or FAIL_ON_RUNNING strategies (7 of 15, a partial kept under the in-between rule). The Cloud support policy sets 99.9 or 99.0 per cent by plan with service credits, and Enterprise goes up to 99.99 per cent (10). The Human task is GA (10). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. 0 + 5 + 0 + 7 + 10 + 10 = 32.

Agent ergonomics Orkes Conductor Human tasks +7

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.

Orkes Conductor Human tasks 69

The MCP server has 19 tools and no read-only subset (15), and the Human task search pages with start and size and filters (20). Averaged to 17 of 25. Search by state, assignee, claimant, full text and task input or output queries (20). Few documented API error responses (10 of 20). Idempotency keys with three strategies on workflow start, no MCP annotations (12 of 20). Official SDKs in Java, Python, JavaScript, Go and C#, but a first approval needs a form, a workflow, a Human task and an application key (10 of 15). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means.

Transparency & trust gotoHuman +7

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.

Orkes Conductor Human tasks 46

Conductor OSS and the SDKs are Apache-2.0, but the forms, assignment policies and Human Tasks API are documented for the proprietary Orkes Conductor (20 of 30). The privacy policy was last updated on 2022-02-23, keeps data 'as long as necessary', mentions no DPA and covers the website more than the cloud product. We found no retention periods for task data (8 of 30). No deprecation policy or dated notices found (5 of 20). The privacy policy says data is stored on servers in the United States, and we found no subprocessor list (8 of 20). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means.

Score by category

CategoryWeightgotoHumanOrkes Conductor Human tasksEdge
Reliability16%2032Orkes Conductor Human tasks +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4965Orkes Conductor Human tasks +16
Agent ergonomics13%6269Orkes Conductor Human tasks +7
Security & auth14%4177Orkes Conductor Human tasks +36
Payments & pricing10%4530gotoHuman +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7781Orkes Conductor Human tasks +4
Transparency & trust7%5346gotoHuman +7
Negative events≤150-1
TotalD 46.2/100C 55.5/100

Facts side by side

FactgotoHumanOrkes Conductor Human tasks
KindHTTP APIPlatform
VendorgotoHumanOrkes
Hosted endpointhttps://api.gotohuman.comhttps://developer.orkescloud.com/api
TransportsHTTP, stdioHTTP, stdio
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
LicenceMIT (SDKs and MCP server)Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)
Tools exposed319
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.conductor-oss/conductor-mcp
Last release2026-11-042026-10-23
Terms last updatedno date givenno date given
Privacy policy last updatedno date given2022-02-23
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Orkes Conductor Human tasks higher.

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.

Orkes Conductor Human tasks

Escalation chains with a time limit per assignee and a choice of leaving the task open or failing the workflow. No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow.

Before you call either

gotoHuman

  1. Call get-form-schema before request-human-review-with-form, since the field data must match the review type
  2. Send agentId and put the review values in data on direct API calls, as the API reference marks both required
  3. Pass a webhookUrl per request when the review type has no default, or the answer has nowhere to go
  4. Deduplicate webhook calls on the Idempotency-Key header, since delivery is at least once
  5. Set your own deadline on the agent side and treat silence as a rejection

Orkes Conductor Human tasks

  1. Give every assignment you want to escalate from a non-zero slaMinutes, since 0 never expires and nothing can follow it
  2. Pick TERMINATE for risky actions so an unanswered approval fails the workflow instead of staying open to anyone
  3. Start approval workflows with an idempotencyKey and RETURN_EXISTING, so a retried start doesn't ask twice
  4. Refresh the JWT from /api/token with a set expiry instead of requesting one that never expires
  5. Fetch single doc pages, not llms.txt, which is the whole documentation in 2.57 MB
  6. Run Conductor OSS v3.30.2 or later if you self-host, since earlier 3.2x versions carry CVE-2026-58138

Questions

Which is better for AI agents, gotoHuman or Orkes Conductor Human tasks?

Orkes Conductor Human tasks scores 55.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 transparency & trust.

Can an agent call gotoHuman and Orkes Conductor Human tasks without installing anything?

Yes. gotoHuman has a hosted endpoint at https://api.gotohuman.com and Orkes Conductor Human tasks at https://developer.orkescloud.com/api.

Are gotoHuman and Orkes Conductor Human tasks open source?

No open-source release is listed for gotoHuman. Orkes Conductor Human tasks is open source (Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)).

Other comparisons with gotoHuman or Orkes Conductor Human tasks

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.