# Qdrant — API Agent Score

> Score: 70/100 (Grade: B) | Domain: qdrant.tech | Rubric: 1.0.0 | Checked: July 24, 2026

Qdrant scored 70/100 (B), classified "partially-ready".

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

## Summary

- Overall: 70/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 63/100 (C)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 74/100 (B)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — 1/1 enums are named types (not bare strings). Investigated: sdk 100%, spec 50%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="master" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://qdrant.tech/documentation/quickstart/ with a runnable first-call sample. Investigated: docs 100%.
- [pass] Description completeness — 79% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://qdrant.tech/documentation/release-notes/. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/qdrant_tech, 10029 snippets). Investigated: docs 100%, cli 100%, sdk 67%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 69%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 13 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No explicit 4xx/5xx codes, but 69 operation(s) document a "default" error response. Investigated: spec 100%, docs 100%.
- [pass] Operation purpose clarity — 99% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 1 of 49 pages have substantive content differences between markdown and HTML (avg 2% missing). Investigated: docs 70%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 1% (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 20 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.

### Agent Usability

- [pass] Sandbox separation — Test credentials signaled (test-key prefixes) but no sandbox server declared in spec. Investigated: spec 100%, docs 100%, sdk 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%.
- [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

Qdrant's API design is a standout strength — the machine-readable contract gives partners and agents a solid foundation to build against. The two areas that most urgently threaten partner program outcomes are agent usability and agent understanding: agents cannot reliably execute real workflows because runnable examples, idempotency guarantees, and rate-limit signaling are absent, and the docs lack the structured, machine-parseable context agents need to act without guessing. Prioritizing executable, trustworthy context and richer agent-readable documentation will unlock self-serve partner integrations and reduce onboarding friction significantly.