$HEADLESS SYSTEMS
03 / Scorecard / Observability

HyperDX

D
Headless Index
38/100
denominator 40
JAIRF
97.2/100
Agent-Optimized
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
HyperDX remains a dashboard-first product with a limited programmatic surface. The Headless Index thesis-fit score of 38/100 sits in the lower band of the index, and JAIRF v1.0.0 puts it at 97.2/100 (Level 4, Agent-Optimized). In practice, vendors at this tier ship enough API to be useful but not enough to be operated end to end by agents without a human in the loop, and the rest of this verdict explains where HyperDX lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. HyperDX is OpenTelemetry-native observability built on ClickHouse. The REST API at app.hyperdx.io exposes logs, traces, metrics, dashboards, alerts, teams, and session replays. SDKs in Node, Python, and a comprehensive OpenTelemetry exporter ecosystem. Open-source under hyperdxio/hyperdx; self-host plus HyperDX Cloud share the API contract.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? Public OpenAPI at github.com/hyperdxio/hyperdx packages/api/openapi.json. The open-source codebase exposes the contract directly. Schema discoverability is solid for self-hostable observability.[2] An agent cannot drive this product end to end today: the headless surface covers basic CRUD but tapers out before reaching the workflows that matter most. On headless operability: On headless operability, the docs crawl did not produce topic coverage sufficient to score programmatic setup, billing, teams, schema, or CLI workflows. A targeted AI review pass should visit the vendor's docs index and confirm what programmatic surfaces actually exist.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: On MCP posture, no official MCP server was detected in the vendor's GitHub organization and no community server was published to the MCP registry under their name. This may change rapidly given the recent MCP adoption curve.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: HyperDX is not a strong target for agent-driven workflows today. The weakest link is API-first posture[5], and the broader surface gives agents too little to operate against. Pick it only when the rest of your stack already mandates it. Use only when locked in.
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 intent5/20
scored

HyperDX is OpenTelemetry-native observability built on ClickHouse. The REST API at app.hyperdx.io exposes logs, traces, metrics, dashboards, alerts, teams, and session replays. SDKs in Node, Python, and a comprehensive OpenTelemetry exporter ecosystem. Open-source under hyperdxio/hyperdx; self-host plus HyperDX Cloud share the API contract.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 0 operations
  • −GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • ·SDKs maintained1 (python); top by stars: hyperdxio/hyperdx-py (5 stars)
cite (3)
  • openapi.url@2026-05-20
  • graphql.probes_tried@2026-05-20
  • github.sdks@2026-05-20
Headless operationUnknown
Unknown

Dashboards, alerts, log queries, trace queries, team and user management, and integration configuration are all programmable. The HyperDX UI is a separate Next.js app consuming the same API. Docker Compose plus Helm chart cover self-host deployment paths.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −API operations exposedOpenAPI present but operations could not be counted
  • ·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 (8)
  • openapi.operations_count@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.topics_found.setup@2026-05-20
  • docs.topics_found.billing@2026-05-20
  • docs.topics_found.teams@2026-05-20
  • docs.topics_found.cli@2026-05-20
  • docs.topics_found.schema@2026-05-20
MCP & agent postureUnknown
Unknown

No first-party HyperDX MCP server has been published. The OTel-native positioning would make MCP integration straightforward; community work is emerging. Most agent-side integration is via the OTel collector rather than via direct API.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·MCP detector statusTimed out during collection (likely GitHub search API rate limit without GITHUB_TOKEN). No verified evidence about MCP presence.
cite (1)
  • mcp.registry_query@2026-05-20
Schema observability10/20
scored

Public OpenAPI at github.com/hyperdxio/hyperdx packages/api/openapi.json. The open-source codebase exposes the contract directly. Schema discoverability is solid for self-hostable observability.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://raw.githubusercontent.com/hyperdxio/hyperdx/main/packages/api/openapi.json (OpenAPI undefined, 0 operations)
  • −GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (2)
  • openapi.url@2026-05-20
  • graphql.probes_tried@2026-05-20
Webhooks & eventsUnknown
Unknown

Alert channels include webhooks with configurable payload templates. Catalog is appropriate for the OpenTelemetry-driven observability use case.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-20
JAIRF · 6 dimensions
FCFoundational Compliance
100/100

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

DXJDeveloper Experience & Tooling Compatibility
100/100

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

ARAXAI-Readiness & Agent Experience
91.1/100

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

AUAgent Usability
100/100

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

SECSecurity
100/100

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

AIDAI Discoverability
90/100

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

Band rationale:D band triggered: HeadlessIndex=38

04 / Embed

Show HyperDX'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.

HyperDX mini badge preview
Get embed code
Peers in Observability
OpenObserveC
Headless Index 43/100
HeliconeC
Headless Index 44/100
LogglyC
Headless Index 46/100
See full Observability ranking →