Let Agents In

Agent readiness · Observability and logging

newrelic.com

8 of 14 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 1 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.

A · Discovery

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • FAIL
    llms.txt publishedllms.txt present at https://newrelic.com/llms.txt, but 1 of the 12 links we sampled across the file are gone, starting with https://newrelic.com/resources/report/state-of-observability-for-retail-ecommerce-2025
  • PASS
    Docs readable without JavaScript6,175 characters of text without JS, on https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/ rather than on https://docs.newrelic.com
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • N/A
    Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
  • PASS
    No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

  • UNMEASURED
    Agent entry pointUnmeasurable: 4 of the 9 known agent entry paths answered with a refusal rather than a file or a 404, so what you publish there is not something we measuredLet ordinary HTTP reach these paths and this becomes measurable.
  • PASS
    OAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
  • PASS
    MCP surfaceLive MCP endpoint at https://mcp.newrelic.com/mcp, answered 401 with an auth challenge

C · Registration

  • FAIL
    No CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML
  • PASS
    Signup reachable without a browserForm renders in server HTML at https://newrelic.com/signup

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 5 documents we read
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://newrelic.com/pricing: "No credit card", "free tier", "Get Started Free"

E · Integration

  • FAIL
    Typed SDK on the registrynewrelic ships without bundled types, matched from the registry by who publishes it rather than by a link on your site
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://docs.newrelic.com, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

Tell me when this changes

The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.

This page is the newest scan we hold for newrelic.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.

Scan a domain yourself