# IMDb — API Agent Score

> Score: 57/100 (Grade: D) | Domain: imdb.com | Rubric: 1.0.0 | Checked: July 24, 2026

IMDb scored 57/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 57/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 72/100 (B)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 58/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples in 4 language(s) across docs (top: shell, typescript, java); 1/13 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — 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.imdb.com/signup (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 4 language(s) across docs (top: shell, typescript, java); 1/13 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. 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 — Indexed on Context7 (duck7000/imdbgraphqlphp, 255 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/29 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 29 pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap present (1 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/29 tested). Investigated: docs 81%.
- [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 3 assessed pages (3 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.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### 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

IMDb's API program shows solid discovery foundations but has critical gaps that block partners and their AI agents from onboarding and integrating with confidence. The two most urgent weaknesses are a complete absence of agent-readable context (no AGENTS.md, no structured docs data, no machine-parseable formats) and a lack of runnable, verifiable API truth — meaning partners and their coding agents are forced to guess at real request/response shapes, auth patterns, and workflows. Prioritize making the API surface legible and executable for both humans and agents, then close the security hygiene and quickstart gaps to complete the partner onboarding story.