# Mintlify — API Agent Score

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

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

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

## Summary

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

## Category Scores

- API Design: 82/100 (A)
- Developer Experience: 85/100 (A)
- Agent Discovery: 98/100 (A+)
- Agent Understanding: 70/100 (B)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [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 85%, docs 70%.
- [warn] Schema coverage & depth — Only 50% of operations have documented schemas. Investigated: spec 70%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [fail] Example coverage — 0% example coverage. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://app.mintlify.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://www.mintlify.com/docs/quickstart with a runnable first-call sample. Investigated: docs 100%.
- [pass] Description completeness — 50% description completeness. Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://www.mintlify.com/docs/changelog. Investigated: spec 100%, docs 100%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt directive found in HTML of 49 of 50 sampled pages (1 missing). Investigated: docs 94%.
- [pass] Registry & SDK presence — Indexed on Context7 (mintlify/docs, 2652 snippets). Investigated: docs 100%, sdk 50%, cli 0%, mcp 0%, wellknown 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### 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] Agent-navigable, token-efficient docs — 2 of 49 pages have substantive content differences between markdown and HTML (avg 3% missing). Investigated: docs 90%.
- [pass] Docs structured data — JSON-LD Article markup on 1/1 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [warn] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 20%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 14% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 1 server entries; no test-key prefixes documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Mintlify's API program shows real strengths in discovery and overall design, but partners and their AI agents face meaningful friction in three areas that matter most for production adoption: agents cannot reliably execute workflows due to missing runnable collections, idempotency guidance, and rate-limit signaling; there is no sandbox separation to de-risk early integration; and there are no AI-readable instructions to orient agents on how to use the API correctly. Fixing operational reliability, safe integration, and agent context should be the immediate priority, followed by closing the remaining onboarding and example gaps to ensure partners can go from discovery to working integration without friction.