Is ZenHub agent-ready?

ZenHub scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.

Does ZenHub publish an OpenAPI spec?

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

What is ZenHub's Headless Index score?

ZenHub scores 42/100 on the Headless Index thesis-fit rubric and sits in Band C in the Project & Task Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Project & Task Management

ZenHub

Headless Index

42/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

ZenHub earns Band C in the Project & Task Management category of The Headless Index, with a thesis-fit score of 42/100. Its strongest dimension is API-first design intent (10/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when ZenHub was scored, which limits how far an agent can go without human integration work.

Editorial verdict

ZenHub is partially headless and partly UI-led. The Headless Index thesis-fit score of 42/100 puts it mid-table on 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 are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where ZenHub lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Zenhub moved to a single GraphQL endpoint (https://api.zenhub.com/public/graphql) and deprecated the REST API whose docs still sit at github.com/ZenHubIO/API with 224 stars, a confusing legacy for anyone starting today. There are no official client libraries in any language. The API is also secondary by design; GitHub holds the issues, Zenhub holds the board metadata. An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Pipelines, workspaces, estimates, epics and issue placement are all reachable as GraphQL mutations, so board automation is genuinely possible. Everything organisational is not: workspace creation, GitHub app installation, sprint configuration and reporting run through the web product. There is no CLI, no Terraform provider and no current self-hosted edition (github.com/ZenHubIO publishes none). Agents move cards, not boards.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Nothing exists. The org (github.com/ZenHubIO) holds four public repos, none MCP related, and the registry query for Zenhub returns no server. No agent documentation, no toolkit, no community server of any standing. For a product whose entire job is telling you the state of work, being invisible to agents is a serious position to hold.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Zenhub does emit workspace webhooks with a small, specific vocabulary (issue_transfer, estimate_set, estimate_cleared, issue_reprioritized), which is enough to mirror board state into another system. Beyond that it is bare: payloads are form encoded rather than JSON, no signature scheme is documented, subscriptions are created in the UI, and there is no retry or replay guarantee. Net assessment: integrators can build agent flows against ZenHub, but the rough edge to plan around is MCP posture^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

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 intent10/20

scored

Zenhub moved to a single GraphQL endpoint (https://api.zenhub.com/public/graphql) and deprecated the REST API whose docs still sit at github.com/ZenHubIO/API with 224 stars, a confusing legacy for anyone starting today. There are no official client libraries in any language. The API is also secondary by design; GitHub holds the issues, Zenhub holds the board metadata.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
·GraphQL endpointDiscovered at https://www.zenhub.com/graphql, introspection disabled or scoped
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation9/20

scored

Pipelines, workspaces, estimates, epics and issue placement are all reachable as GraphQL mutations, so board automation is genuinely possible. Everything organisational is not: workspace creation, GitHub app installation, sprint configuration and reporting run through the web product. There is no CLI, no Terraform provider and no current self-hosted edition (github.com/ZenHubIO publishes none). Agents move cards, not boards.

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 posture4/20

scored

Nothing exists. The org (github.com/ZenHubIO) holds four public repos, none MCP related, and the registry query for Zenhub returns no server. No agent documentation, no toolkit, no community server of any standing. For a product whose entire job is telling you the state of work, being invisible to agents is a serious position to hold.

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)

ai_review_browser.mcp@2026-08-19

Schema observability10/20

scored

GraphQL is the saving grace here. The endpoint is live and introspection is available once a personal API key is attached, so a client can be generated from the schema rather than from prose. The catch is that nothing is fetchable anonymously (an unauthenticated POST returns HTTP Token: Access denied), and no SDL file is published in any repository.

signals (3)

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

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events9/20

scored

Zenhub does emit workspace webhooks with a small, specific vocabulary (issue_transfer, estimate_set, estimate_cleared, issue_reprioritized), which is enough to mirror board state into another system. Beyond that it is bare: payloads are form encoded rather than JSON, no signature scheme is documented, subscriptions are created in the UI, and there is no retry or replay guarantee.

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)

ai_review_browser.webhooks@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:C band: scores 40-75 range

04 / Embed

Show ZenHub'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 Project & Task Management

WrikeC

Headless Index 44/100

CloseC

Headless Index 44/100

AttioC

Headless Index 44/100

See full Project & Task Management ranking →

FAQ

ZenHub and agent readiness

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