# imgix — API Agent Score

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

imgix scored 63/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 61/100 (C)
- Developer Experience: 72/100 (B)
- Agent Discovery: 84/100 (A)
- Agent Understanding: 63/100 (C)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — 0/12 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 60%.
- [pass] Example coverage — Code samples in 4 language(s) across docs (top: javascript, python, ruby); 1/8 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 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] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://dashboard.imgix.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: javascript, python, ruby); 1/8 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [warn] Description completeness — 5/6 operations carry a description. Investigated: sdk 83%.
- [warn] Changelog published — Newest official SDK activity 188 days ago — drifting from the contract. Investigated: sdk 50%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/imgix, 3769 snippets). Investigated: docs 100%, sdk 58%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 64%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "Error" with 6 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — 1 of 50 sampled pages appear to be client-side rendered SPA shells (__next detected); agents using HTTP fetches will see no content; 5 more have page structure but little substantive content. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 3% (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 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.

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

Imgix's agent discovery posture is a genuine strength — your APIs are findable and docs are reachable without a sales conversation. However, two areas are holding back partner program outcomes: agents and partners cannot reliably understand how to authenticate, handle errors, or run real workflows against your API (agent understanding and usability are both critically weak), and the API contract itself lacks the security and governance signals partners need to trust it in production. Prioritize making your API executable and self-explanatory for both human developers and AI coding agents first, then close the contract and documentation gaps that prevent partners from building with confidence.