Head to head · Human approval · October 2026 research run

Orkes Conductor Human tasks vs withHuman

withHuman scores 71.5 (BB) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 6 of 7 scored categories. 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

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.

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

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

withHuman BB

Best for Teams that want tool calls from coding agents or their own agents held for approval by rules, with escalation and an audit log, and no review UI to build.

Ahead on

  • Reliability, 56 against 32
  • Schema & documentation, 91 against 65
  • Agent ergonomics, 86 against 69
  • Security & auth, 83 against 77
  • Payments & pricing, 45 against 30
  • Transparency & trust, 75 against 46

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No published request rate limits, and no uptime guarantee outside an enterprise agreement

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.

Transparency & trust withHuman +29

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.

withHuman 75

Closed hosted service with short, clear terms (effective 13 October 2026). The self-hosted core is public at github.com/withHumanAI/withHuman under the Elastic License 2.0, which is source-available rather than an OSI licence, though the site calls it open source (18 of 30). The privacy policy (effective 16 October 2026) and terms agree on no model training, server logs kept 30 days and records kept for the life of the organisation, and the processor list now names Microsoft Azure for the AI Judge models. The purge after deletion is only 'a short grace period' and no DPA was found (21 of 30). The terms promise notice of removals and 14 days' email notice of material changes to the terms, with no dated deprecation policy (5 of 20). Processors are named with purposes, hosting is Azure North Europe (Ireland) and the AI Judge models run in Sweden Central (20). 18 + 21 + 5 + 20 = 64.

Schema & documentation withHuman +26

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.

withHuman 91

A public OpenAPI 3.1 document, version 1.0.0, with 124 operations, also served by each instance at /api/openapi.yaml (25). llms.txt lists every docs page with a Markdown copy (10). Operation descriptions state purpose, preconditions and what each credential may do, and the docs separate the MCP server from the MCP gateway (16 of 20). Enums for status, required fields and bounded durations are typed. arguments, context and instance metadata are free-form objects by design (12 of 15). Each operation has a curl example, sample responses and a response table, and the error envelope has a table of stable types (13 of 15). Paths are versioned (/api/aap/v1, /api/v1), the document is versioned, and a public changelog at withhuman.ai/changelog dates each release from 3 October to 4 November 2026 (15). 25 + 10 + 16 + 12 + 13 + 15 = 91.

Reliability withHuman +24

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.

withHuman 56

Graded as a hosted service. The site footer now links status.withhuman.ai, an incident.io page with six components (Website, Web app, API, MCP gateway, Notifications, Mobile apps) and data from 22 October 2026 (20). It has never posted an incident, so it is a short record (15). No request rate limits are published. 429 is documented only for the plan's limit on pending requests or active agents, and gateway calls and approval requests are unlimited on every plan (0). Idempotency-Key is required on four write commands, request creation among them, with documented replay and conflict behaviour, and the long-poll guide says to call again after a dropped connection. No Retry-After or backoff guidance for 429 was found. No settled value covers idempotency keys without 429 guidance, so the 8 October partial is kept (11 of 15, as hunter). The terms give no uptime guarantee outside an enterprise agreement (0). The provider API reached version 1.0.0 on 13 October 2026, and the terms effective that day no longer describe early access (10). 20 + 15 + 0 + 11 + 0 + 10 = 56.

Agent ergonomics withHuman +17

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.

withHuman 86

The approval surface is 9 operations and a request needs three fields. List endpoints take limit (17 of 25). limit on list operations, cursor or offset, q, status filters and eight audit filters (16 of 20). Errors carry a stable type and code, a request_id and structured details, with 409, 412 and 428 codes an agent can act on (18 of 20). Mandatory idempotency keys and If-Match on revision activation, and the MCP server's tools carry read-only, destructive and idempotent annotations in the published source (20). Sensible defaults and few required parameters, with Python (agentapprovalprotocol) and TypeScript (@agentapprovalprotocol/sdk) SDKs announced on 13 October and used in the repository's examples (15). 17 + 16 + 18 + 20 + 15 = 86.

Payments & pricing withHuman +15

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.

withHuman 45

No machine payment protocol (0). Public plan prices, Free at $0 for up to 5 members and Scale at $20 per user a month, with no per-request price (10). The Free plan and trial need no subscription per the billing docs. We did not sign up to confirm that no card is asked for (20). A person signs up in a browser and approves each agent's enrolment. Provisioner tokens then issue instance credentials by API (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.

Security & auth withHuman +6

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.

withHuman 83

Purpose-limited credentials. An agent credential can only create and read its own requests, a provisioner token only manages instances, personal keys can be narrowed and expire after 90 days by default, and the MCP server uses OAuth with PKCE, dynamic client registration and 35 scopes. Choosing specific actions is limited to the hosted paid plans (28 of 30). Agents and organisation keys can never decide a request, sensitive grants need a recent sign-in, and on 8 October the docs said the required-MFA settings don't yet work with the built-in sign-in methods, not re-read on 4 November (16 of 20). Reviewers see agent reasoning as a claim separate from the arguments, server is documented as an unverified label, and notifications never carry arguments (11 of 15). Append-only audit log with search by API, and every key's changes recorded under the key, in the hosted edition (13 of 15). security.txt on both hosts names security@withhuman.ai and the policy at withhuman.ai/security, which promises a reply usually within one working day, with private GitHub reports for the core. The trust page says Metoro's SOC 2 Type II report covers withHuman and is shared under a nondisclosure agreement. No bounty or published advisory yet (15 of 20). 28 + 16 + 11 + 13 + 15 = 83.

Score by category

CategoryWeightOrkes Conductor Human taskswithHumanEdge
Reliability16%3256withHuman +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6591withHuman +26
Agent ergonomics13%6986withHuman +17
Security & auth14%7783withHuman +6
Payments & pricing10%3045withHuman +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8178Orkes Conductor Human tasks +3
Transparency & trust7%4675withHuman +29
Negative events≤15-1-2
TotalC 55.5/100BB 71.5/100

Facts side by side

FactOrkes Conductor Human taskswithHuman
KindPlatformHTTP API
VendorOrkesMetoro Inc
Hosted endpointhttps://developer.orkescloud.com/apihttps://app.withhuman.ai
TransportsHTTP, stdioHTTP
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicenceApache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)Proprietary hosted service under Metoro Inc's terms. The self-hosted core is source-available under the Elastic License 2.0 at https://github.com/withHumanAI/withHuman
Tools exposed19none
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.conductor-oss/conductor-mcpnot listed
Last release2026-10-232026-10-08
Terms last updatedno date given2026-09-04
Privacy policy last updated2022-02-232026-09-04
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot 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/5 (2)none

How the scores have moved

Verdicts

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.

withHuman

withHuman's approval API is small and carefully specified, with a public OpenAPI 1.0.0 document, mandatory idempotency keys and agent credentials that can never approve, and the core is public under the Elastic License 2.0. No request rate limits or SLA outside enterprise contracts are published, and the status page has history only from 22 October 2026.

Before you call either

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

withHuman

  1. Send an Idempotency-Key header on POST /api/aap/v1/requests. The call answers 400 without one
  2. Read the decision with GET /api/aap/v1/requests/{id}?wait=30s and repeat while status is pending. wait is capped at 30 seconds
  3. Set timeout between one second and seven days, and treat expired and cancelled as a refusal
  4. Start an approved call within five minutes of decided_at, because the decision carries an expires_at
  5. Cancel a request when you stop waiting, so reviewers stop seeing it

Questions

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

withHuman scores 71.5 (BB) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 6 of 7 scored categories.

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

Yes. Orkes Conductor Human tasks has a hosted endpoint at https://developer.orkescloud.com/api and withHuman at https://app.withhuman.ai.

Are Orkes Conductor Human tasks and withHuman open source?

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

Other comparisons with Orkes Conductor Human tasks or withHuman

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.