Compare

Hyperdx vs New Relic

New Relic scores higher on the AgentReady, 51/100 against 43/100. They differ on 6 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Hyperdx. An open source observability platform that unifies session replays, logs, traces, metrics and errors.

New Relic. Intelligent Observability platform that resolves issues at scale before they impact bottom line

Where Hyperdx is ahead

Hyperdx passes no mandatory sales call, and New Relic does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.

Where New Relic is ahead

New Relic passes clear product positioning, llms.txt published and machine-readable metadata, and Hyperdx does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds adopt: cli available. Hyperdx misses it.

And on operate, observable execution. Hyperdx misses it.

What neither does

Both fail llms-full.txt / full agent docs, mcp discoverable, structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, programmatic credential creation, mcp integration available, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover is whether an agent can find the product at all without being told it exists. New Relic leads 80 to 53. Hyperdx misses clear product positioning, llms.txt published, llms-full.txt / full agent docs, mcp discoverable, machine-readable metadata; New Relic misses llms-full.txt / full agent docs, mcp discoverable.

Understand. Both sit at 23/100 here. Hyperdx misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; New Relic misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. Hyperdx leads 70 to 65. Hyperdx misses programmatic credential creation, cli available, mcp integration available; New Relic misses no mandatory sales call, programmatic credential creation, mcp integration available.

Operate. New Relic leads 35 to 24. Hyperdx misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified; New Relic misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

Hyperdx starts at $20/mo and has a free tier. New Relic does not publish one and has a free tier.

Signal by signal

Which to pick

New Relic clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Hyperdx and New Relic. Alternatives to each: Hyperdx, New Relic.

An agent can fetch this as data: POST /v1/compare {"slugs": ["hyperdx", "newrelic"]}