# NexHealth — API Agent Score

> Score: 69/100 (Grade: C) | Domain: nexhealth.com | Rubric: 1.0.0 | Checked: July 29, 2026

NexHealth scored 69/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 54/100 (D)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 75/100 (B)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → dist/types/index.d.ts. Investigated: sdk 100%, spec 78%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 83%, docs 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 13% example coverage. Investigated: spec 100%, sdk 100%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.nexhealth.com/sign-up; no free tier or sandbox language detected. Investigated: docs 100%.
- [warn] Description completeness — 56% description completeness. Investigated: spec 17%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/nexhealth, 11248 snippets). Investigated: docs 100%, sdk 42%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — Could not test any pages; 1 failed to fetch. Investigated: docs 60%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 1 pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 2 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, spec 50%.
- [warn] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 67%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 25 list endpoint(s). Investigated: spec 100%, docs 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.

## Executive Summary

Nexhealth's API program has a strong foundation in API design, with a machine-readable, well-structured contract that partners and agents can build against. However, the program's two most critical gaps are in Developer Experience and Agent Usability: partners have no changelog to track breaking changes, no quickstart to get hands-on quickly, and agents lack the operational signals — idempotency guidance and rate-limit headers — needed to run reliable workflows without manual intervention. Addressing versioning transparency, agent-readiness context, and operational reliability should be the immediate priority to unlock self-serve partner growth.