# NRG — API Agent Score

> Score: 46/100 (Grade: F) | Domain: nrg.com | Rubric: 1.0.0 | Checked: August 6, 2026

NRG scored 46/100 (F), classified "not-ai-ready".

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

## Summary

- Overall: 46/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 43/100 (F)
- Developer Experience: 40/100 (F)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 49/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Example coverage — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%, sdk 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [fail] Self-service developer portal — No self-service signup detected: no signup link found on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved. Investigated: docs 0%.
- [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 1 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 3 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.nrg.com/llms.txt, https://docs.nrg.com/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. Investigated: docs 57%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 2% (threshold 35% for full credit).
- [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 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Nrg's API program has meaningful strengths in crawlability and documentation reachability, but the partner experience breaks down in two critical areas: the API contract itself lacks the schema depth and worked examples that partners and their agents need to build confidently, and there is no self-service onboarding path — no portal, no quickstart, no code samples. Layered on top, agents cannot discover or parse the API surface without manual intervention. Prioritize standing up a self-service developer portal generated from a hardened OpenAPI spec, then close the agent-readiness gaps so both human partners and the tools they use can reach a first successful call without a sales conversation.