Home / The Index / New Relic
Lagging

How agent-ready is New Relic?

Independent agentability audit of New Relic, scored across the 8 principles of Agent Factors Engineering — how well AI agents can parse, navigate, and operate it.

Audited June 12, 2026 · Rubric v0 · 3 page(s) evaluated

Audit summary

New Relic's agentability audit returned scores of 33/100 on the homepage, 42/100 on pricing, and 44/100 on documentation, indicating significant friction for autonomous AI agents attempting to parse and operate the site. The platform performs adequately on status feedback (65/100) and machine readability (54/100), but falls short in areas critical to agent interaction.

The most severe gaps appear in transparency (0/100), shadow UI avoidance (15/100), control (19/100), and defaults (23/100). These scores suggest that agents will struggle to understand output confidence, interact with UI elements reliably, safely execute or reverse actions, and work efficiently without manual input of common values. Improving these dimensions would materially increase New Relic's compatibility with agent-driven workflows.

Score by principle

Machine Readability54 / 100
Chunking36 / 100
Control19 / 100
Status65 / 100
Defaults23 / 100
Clean Handoffs50 / 100
No Shadow UI15 / 100
Transparency0 / 100

Key findings

Defaults
Pre-fill inputs with sensible defaults wherever a reasonable one exists.
Transparency
Surface confidence/certainty on key outputs (a confidence field in API responses, or a 'verified vs best-guess' label in the UI).
Transparency
Offer a one-line summary plus an expandable drill-down for important results.
Transparency
Attach source references or input citations (link or id) to generated outputs.
Control
Gate destructive actions behind an explicit, distinctly-labelled confirmation step — not a same-styled button.
Control
Provide a labelled pause/cancel/stop control for long-running actions; give it an accessible name like 'Cancel import', not a bare icon.
Status
Among the stronger areas for New Relic, scored 65/100.
Machine Readability
Among the stronger areas for New Relic, scored 54/100.
Clean Handoffs
Among the stronger areas for New Relic, scored 50/100.

How New Relic could improve its score

To improve agentability, New Relic should prioritize the following fixes identified in the audit:

  • Add confidence indicators to API responses and UI outputs, such as a numeric confidence field or 'verified vs best-guess' labels, so agents can assess reliability of returned data.
  • Implement collapsible result summaries that provide a one-line overview with expandable drill-downs, and attach source references or input citations to generated outputs for traceability.
  • Pre-fill form inputs with sensible defaults wherever reasonable values exist, reducing the need for agents to supply boilerplate configuration.
  • Gate destructive actions behind explicit, distinctly-labelled confirmation steps rather than same-styled buttons, and support undo or override capabilities on completed destructive changes.
  • Provide clearly labelled pause, cancel, or stop controls with accessible names like 'Cancel import' for long-running operations, avoiding icon-only buttons.
  • Fix heading hierarchy by using a single <h1> per page and ensuring no levels are skipped, enabling agents to parse document structure correctly.

Work at New Relic? Re-audit any page free.

Scores refresh automatically when we re-crawl — or run an instant audit on any URL now.

Run a free audit

Embed this score

Show your agent-readiness in your docs or README. The badge links back to this live report.

<a href="https://agentability.io/index/new-relic.html"> <img src="https://agentability.io/badge/new-relic.svg" alt="New Relic — Agentability score 33/100 (Lagging)" /> </a>