# New Relic — API Agent Score

> Score: 67/100 (Grade: C) | Domain: newrelic.com | Rubric: 1.0.0 | Checked: July 24, 2026

New Relic scored 67/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/newrelic)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 67/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 66/100 (C)
- Agent Discovery: 68/100 (C)
- Agent Understanding: 44/100 (F)
- Agent Usability: 74/100 (B)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="v2") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — Medium parameter complexity (avg 2.4 params/op; nested/body schemas present). Investigated: spec 83%, sdk 71%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://newrelic.com/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Description completeness — 98% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 29%.
- [pass] Changelog published — changelog documented in the docs site at https://docs.newrelic.com/docs/release-notes/. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 2 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/pulumi_registry_packages_newrelic, 4070 snippets). Investigated: docs 100%, cli 100%, mcp 100%, sdk 67%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap present (2 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.newrelic.com/llms.txt, https://docs.newrelic.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 67%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 5% (threshold 35% for full credit).
- [fail] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 2 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — Pagination params detected on 1 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

New Relic's API design is a clear strength — the schema and contract surface is well-structured and machine-readable. However, agent understanding is critically weak across the board: AI agents and partners cannot reliably discover, interpret, or act on the APIs without guessing at operation intent, error meaning, and workflow context. Discovery also has a meaningful gap, as no llms.txt or agent-oriented front door exists. Prioritize closing the agent understanding gaps first — they block every downstream integration — then shore up discovery and runnable onboarding to compress the time to a partner's first successful call.