Is Cadence agent-ready?

Cadence scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is headless operation; its weakest is MCP and agent posture.

Does Cadence publish an OpenAPI spec?

No published OpenAPI specification was found when Cadence was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Cadence's Headless Index score?

Cadence scores 65/100 on the Headless Index thesis-fit rubric and sits in Band B in the Workflow & Automation category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Workflow & Automation

Cadence

Headless Index

65/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Cadence earns Band B in the Workflow & Automation category of The Headless Index, with a thesis-fit score of 65/100. Its strongest dimension is headless operation (17/20); its weakest scored dimension is MCP and agent posture (5/20). No public OpenAPI specification was found when Cadence was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Cadence is solidly built for programmatic consumption. The Headless Index thesis-fit score of 65/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Cadence lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Cadence has no REST API and does not want one. Its contract is a versioned gRPC and Thrift IDL kept in a public repository (github.com/cadence-workflow/cadence-idl), where service_workflow.proto and service_visibility.proto define the operations. Official clients exist for Go, Java and Python (cadence-go-client, cadence-java-client). Code generation from proto is the intended path, and it genuinely works. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Everything runs from code. The cadence CLI handles domain registration, workflow start, signal, query and history inspection; Helm charts deploy the server (github.com/cadence-workflow/cadence-charts); cadence-web is optional decoration. Because the whole system is Apache-licensed and self-hosted, no vendor console can hold state hostage. Workflow logic is Go or Java, which raises the authoring floor for agents.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: There is no MCP server under the org, no registry entry, and no agent-facing documentation on cadenceworkflow.io. For an orchestration engine agents would plausibly want to drive, starting and querying long-running executions, that absence carries weight. The gRPC surface is clean enough that a wrapper would be straightforward, yet nobody official has built one (github.com/cadence-workflow).^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Cadence emits no webhooks, deliberately. What it holds instead is a durable per-execution event history with typed entries such as WorkflowExecutionStarted, ActivityTaskScheduled and TimerFired, readable through GetWorkflowExecutionHistory (proto/uber/cadence/api/v1/history.proto). That is a richer audit trail than most webhook catalogues, but it is pull-only. Agents must poll, or run a worker to react. Net assessment: Cadence can be operated by agents for the majority of practical workflows. The closest thing to a gap is MCP posture^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent16/20

scored

Cadence has no REST API and does not want one. Its contract is a versioned gRPC and Thrift IDL kept in a public repository (github.com/cadence-workflow/cadence-idl), where service_workflow.proto and service_visibility.proto define the operations. Official clients exist for Go, Java and Python (cadence-go-client, cadence-java-client). Code generation from proto is the intended path, and it genuinely works.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 17 probe paths
·GraphQL endpointDiscovered at https://cadenceworkflow.io/graphql, introspection disabled or scoped
+SDKs maintained4 (go, java, python); top by stars: cadence-workflow/cadence-go-client (382 stars)
+SDK recency3 of 4 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-19)

cite (1)

github.sdks@2026-08-19

Headless operation17/20

scored

Everything runs from code. The cadence CLI handles domain registration, workflow start, signal, query and history inspection; Helm charts deploy the server (github.com/cadence-workflow/cadence-charts); cadence-web is optional decoration. Because the whole system is Apache-licensed and self-hosted, no vendor console can hold state hostage. Workflow logic is Go or Java, which raises the authoring floor for agents.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture5/20

scored

There is no MCP server under the org, no registry entry, and no agent-facing documentation on cadenceworkflow.io. For an orchestration engine agents would plausibly want to drive, starting and querying long-running executions, that absence carries weight. The gRPC surface is clean enough that a wrapper would be straightforward, yet nobody official has built one (github.com/cadence-workflow).

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

github.sdks@2026-08-19

Schema observability17/20

scored

Protobuf definitions under proto/uber/cadence/api/v1 are fetchable without authentication and cover domains, workflows, tasklists, schedules and visibility. An agent can generate a client cold from the IDL with no prose reading whatsoever (github.com/cadence-workflow/cadence-idl). The cost is that protobuf is less directly usable to a model than JSON Schema, and no OpenAPI rendering is published.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 17 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://cadenceworkflow.io/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events10/20

scored

Cadence emits no webhooks, deliberately. What it holds instead is a durable per-execution event history with typed entries such as WorkflowExecutionStarted, ActivityTaskScheduled and TimerFired, readable through GetWorkflowExecutionHistory (proto/uber/cadence/api/v1/history.proto). That is a richer audit trail than most webhook catalogues, but it is pull-only. Agents must poll, or run a worker to react.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

github.sdks@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:B band: JAIRF=N/A HeadlessIndex=65

04 / Embed

Show Cadence's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Workflow & Automation

TemporalC

Headless Index 66/100

PipedreamB

Headless Index 64/100

ActivepiecesC

Headless Index 66/100

See full Workflow & Automation ranking →

FAQ

Cadence and agent readiness

Is Cadence agent-ready?: Cadence scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is headless operation; its weakest is MCP and agent posture.
Does Cadence publish an OpenAPI spec?: No published OpenAPI specification was found when Cadence was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Cadence's Headless Index score?: Cadence scores 65/100 on the Headless Index thesis-fit rubric and sits in Band B in the Workflow & Automation category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.