# Netflix — API Agent Score

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

Netflix scored 65/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 100/100 (A+)
- Developer Experience: 61/100 (C)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 60/100 (C)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → lib/index.d.ts. Investigated: sdk 100%.
- [pass] Security & governance hygiene — security.txt valid at https://netflix.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 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

- [pass] Self-service developer portal — Signup page at https://www.netflix.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 6 day(s) ago. Investigated: 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 1 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (spring-cloud/spring-cloud-netflix, 218 snippets). Investigated: docs 100%, sdk 67%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://netflix.github.io/llms.txt, https://netflix.github.io/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 86%.
- [warn] Machine-readable errors (RFC 9457) — Single base error "null" present, but only 1 subclass found; a richer hierarchy lets consumers catch narrowly. Investigated: sdk 50%.
- [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] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [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.

## Executive Summary

Netflix's API program shows strength in agent discovery and crawlability, but two areas are holding partners back: agents and AI coding tools cannot reliably interpret or act on the API surface without structured context, and partners lack the runnable, tested examples needed to integrate quickly and confidently. Closing the gaps in agent-readable instructions and onboarding materials should be the immediate priority, followed by ensuring every workflow partners care about is executable and idempotency-safe out of the box.