$HEADLESS SYSTEMS
03 / Scorecard / Observability

Mezmo

C
Headless Index
54/100
JAIRF
N/A
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
Mezmo is partially headless and partly UI-led. The Headless Index thesis-fit score of 54/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 Mezmo lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Mezmo (formerly LogDNA) exposes Telemetry Pipeline and log-analysis REST APIs. SDKs in Node, Python, Ruby, Go, and Java cover the LogDNA-era surface with growing coverage for the newer pipeline product. The brand transition from LogDNA shows in the API; some surfaces are mature, others are still being modernised.[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? REST documented across the docs site; no single canonical OpenAPI URL prominently exposed. Schema discoverability is doc-based.[2] 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, sources, sinks, alerts, and views are programmable. The Terraform provider continues to expand. Self-host (Edge) plus Mezmo Cloud share most of the surface.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Mezmo MCP server. The product is mid-tier observability; MCP integration is community-led.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Alert webhooks with custom payload templates and HMAC options. The LogDNA legacy means the webhook product is mature even where the rest of the API is being modernised. Net assessment: integrators can build agent flows against Mezmo, but the rough edge to plan around is MCP posture[5]. 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 intent14/20
scored

Mezmo (formerly LogDNA) exposes Telemetry Pipeline and log-analysis REST APIs. SDKs in Node, Python, Ruby, Go, and Java cover the LogDNA-era surface with growing coverage for the newer pipeline product. The brand transition from LogDNA shows in the API; some surfaces are mature, others are still being modernised.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • OpenAPI specNot found across 34 probe paths
  • ·GraphQL endpointDiscovered at https://www.mezmo.com/graphql, introspection disabled or scoped
  • SDKs maintainedNone detected in vendor org
cite (1)
  • github.sdks@2026-05-20
Headless operation14/20
scored

Pipelines, sources, sinks, alerts, and views are programmable. The Terraform provider continues to expand. Self-host (Edge) plus Mezmo Cloud share most of the surface.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • 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)
  • github.sdks@2026-05-20
MCP & agent posture4/20
scored

No first-party Mezmo MCP server. The product is mid-tier observability; MCP integration is community-led.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • 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)
  • mcp.found@2026-05-20
Schema observability10/20
scored

REST documented across the docs site; no single canonical OpenAPI URL prominently exposed. Schema discoverability is doc-based.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • OpenAPINot discovered across 34 standard probe paths
  • ·GraphQL introspectionGraphQL endpoint at https://www.mezmo.com/graphql but introspection is disabled, scoped, or behind authentication
cite (1)
  • openapi.discovered@2026-05-20
Webhooks & events12/20
scored

Alert webhooks with custom payload templates and HMAC options. The LogDNA legacy means the webhook product is mature even where the rest of the API is being modernised.

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)
  • ai_review_browser.webhooks@2026-05-20
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

Powered by JAIRF v1.0.0 by Jentic

Band rationale:C band: scores 40-75 range

04 / Embed

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