Is Netdata agent-ready?

Netdata scores Band B on The Headless Index and rates AI-Ready on JAIRF (81.8/100). Its strongest area for agent use is MCP and agent posture; its weakest is webhooks and events.

Does Netdata publish an OpenAPI spec?

Yes. Netdata publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.

What is Netdata's Headless Index score?

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

03 / Scorecard / Observability

Netdata

Headless Index

72/100

JAIRF

81.8/100

AI-Ready

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Netdata earns Band B in the Observability category of The Headless Index, with a thesis-fit score of 72/100 and a JAIRF rating of 81.8/100 (AI-Ready). Its strongest dimension is MCP and agent posture (18/20); its weakest scored dimension is webhooks and events (8/20). Netdata publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict

Netdata is solidly built for programmatic consumption. The Headless Index thesis-fit score of 72/100 lands it in the upper-middle of the index, and JAIRF v1.0.0 puts it at 81.8/100 (Level 3, AI-Ready). 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 Netdata lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. The agent answers on three parallel API versions, with v3 the live one (/api/v3/data, /api/v3/alerts, /api/v3/functions, /api/v3/q), and it is genuinely queryable without the Cloud UI. What is missing is a client library in any server language; the only published package is a chart renderer (@netdata/charts on npm), which tells you who the API was written for. 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: Agent side is file-driven and complete: netdata.conf, health alarm files, go.d collector configs and a Helm chart install without a browser. Cloud is scriptable too, through an official provider covering spaces, rooms, members and notification channels (netdata/terraform-provider-netdata, resources space, room_member, notification_slack_channel). It is young at version 0.4.2, and alert rule authoring still happens in the web configuration manager.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Netdata compiled MCP into the agent itself rather than shipping a side project. The server lives in the main repo (netdata/netdata src/web/mcp) and answers on /mcp streamable HTTP and /sse, with the nd-mcp bridge for stdio clients and documented setup for Claude Code and Cursor. Cloud-wide MCP is still marked unavailable, so visibility stops at the parent node.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Cloud offers a webhook notification target with careful transport security, supporting mutual TLS, basic and bearer authentication plus a verification token from a test send. That is a delivery channel, not an event system. There is no named event catalogue, no HMAC body signature and no documented retry or replay; agents poll instead (/api/v3/alert_transitions). Net assessment: Netdata can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events^[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 intent14/20

scored

The agent answers on three parallel API versions, with v3 the live one (/api/v3/data, /api/v3/alerts, /api/v3/functions, /api/v3/q), and it is genuinely queryable without the Cloud UI. What is missing is a client library in any server language; the only published package is a chart renderer (@netdata/charts on npm), which tells you who the API was written for.

signals (6)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPI specPublished, 72 operations
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
+SDKs maintained3 (go, javascript, rust); top by stars: netdata/charts (16 stars)
+SDK recency2 of 3 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-14)
·npm weekly downloads703 across published packages; top: @netdata/charts @ 703/week

cite (1)

github.sdks@2026-08-19

Headless operation16/20

scored

Agent side is file-driven and complete: netdata.conf, health alarm files, go.d collector configs and a Helm chart install without a browser. Cloud is scriptable too, through an official provider covering spaces, rooms, members and notification channels (netdata/terraform-provider-netdata, resources space, room_member, notification_slack_channel). It is young at version 0.4.2, and alert rule authoring still happens in the web configuration manager.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
·API operations exposed72 operations in OpenAPI spec
·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 posture18/20

scored

Netdata compiled MCP into the agent itself rather than shipping a side project. The server lives in the main repo (netdata/netdata src/web/mcp) and answers on /mcp streamable HTTP and /sse, with the nd-mcp bridge for stdio clients and documented setup for Claude Code and Cursor. Cloud-wide MCP is still marked unavailable, so visibility stops at the parent node.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/netdata/netdata (80232 stars, last commit 0 days ago)
−Community MCP serversNone found
+Agent-friendly SDKs1 TS/JS SDKs available; top: @netdata/charts (703/week downloads)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability16/20

scored

A real OpenAPI 3.0 document ships in the repository and is fetchable raw (raw.githubusercontent.com/netdata/netdata/master/src/web/api/netdata-swagger.yaml), covering v1, v2 and v3 endpoints with parameter and response definitions. An agent can generate a client cold. The document stops at the agent boundary, so anything Netdata Cloud adds on top is undocumented in machine-readable form.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPIPublished at https://raw.githubusercontent.com/netdata/netdata/master/src/web/api/netdata-swagger.yaml (OpenAPI 3.0.0, 72 operations)
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events8/20

scored

Cloud offers a webhook notification target with careful transport security, supporting mutual TLS, basic and bearer authentication plus a verification token from a test send. That is a delivery channel, not an event system. There is no named event catalogue, no HMAC body signature and no documented retry or replay; agents poll instead (/api/v3/alert_transitions).

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

FCFoundational Compliance

70/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility

86.7/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience

83/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability

100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity

55/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability

99.2/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:B band: JAIRF=81.8 HeadlessIndex=72

04 / Embed

Show Netdata'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

Calibration

How THI compares to external scorers

Source	Score	Measures	Last checked
Fern Agent Score	not found	Documentation completeness and SDK shape (~22 checks)	—
CLIRank Agent Friendliness	not found	CLI readiness, docs quality, and overall agent affordances	—
Cloudflare Is It Agent Ready?	blocked	Cloudflare's manual agent-readiness heuristic per vendor URL	—
Jentic Scorecard	—	JAIRF-based scorecard requiring a public OpenAPI specification	—

THI 72 vs external median 0

No external scores available to calibrate against.

Peers in Observability

DynatraceB

Headless Index 72/100

VictoriaMetricsB

Headless Index 70/100

RollbarB

Headless Index 74/100

See full Observability ranking →

FAQ

Netdata and agent readiness

Is Netdata agent-ready?: Netdata scores Band B on The Headless Index and rates AI-Ready on JAIRF (81.8/100). Its strongest area for agent use is MCP and agent posture; its weakest is webhooks and events.
Does Netdata publish an OpenAPI spec?: Yes. Netdata publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.
What is Netdata's Headless Index score?: Netdata scores 72/100 on the Headless Index thesis-fit rubric and sits in Band B in the Observability category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.