# Clarivate — API Agent Score

> Score: 73/100 (Grade: B) | Domain: clarivate.com | Rubric: 1.0.0 | Checked: October 14, 2026

Clarivate scored 73/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 92/100 (A+)
- Developer Experience: 58/100 (D)
- Agent Discovery: 82/100 (A)
- Agent Understanding: 74/100 (B)
- Agent Usability: 59/100 (D)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: docs 100%, spec 50%, wellknown 50%.
- [warn] Machine-readable, versioned contract — The API sets a version ("1.0.7") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 85%, docs 70%.
- [warn] Schema coverage & depth — Only 60% of the 10 operations document request and response schemas, so an agent can't do function-calling against most endpoints. Investigated: spec 77%, sdk 27%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 15%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://access.clarivate.com/login?app=cadp&client_id=f4d085c9-30ee-4a31-b4a8-259e6666a9df&redirect_uri=https%3A%2F%2Fapi.clarivate.com%2Fauth%2Fclarivate%2Fcallback&response_type=code&scope=profile%20email, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Description completeness — Only 50% of operations and parameters have descriptions (0 of 2 ops, 0 of 0 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%, sdk 70%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [fail] Code samples in docs — No code samples detected across 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_clarivate, 424 snippets). Investigated: docs 100%, sdk 25%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.clarivate.com/llms.txt, https://developer.clarivate.com/docs/llms.txt). Investigated: docs 50%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Operation purpose clarity — Read/write classification is mostly ambiguous: only 16/270 operations classified. Investigated: sdk 53%, spec 30%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 4% (threshold 35% for full credit).
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 1 assessed pages (1 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [warn] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 5%, docs 5%.
- [fail] Pagination documented & consistent — List endpoints offer no pagination, so an agent can't page through large collections. Investigated: spec 0%, docs 0%.

## Executive Summary

Clarivate's API program shows strong API design and discoverability fundamentals, but partners and their agents face a steep onboarding barrier: there is no quickstart, no code samples, and no changelog — meaning a new partner must figure out first steps from scratch and has no way to anticipate breaking changes. Structured data gaps further prevent answer engines from surfacing Clarivate's APIs in AI-driven search. Prioritize fast-path onboarding and change transparency first, then close the structured data and pagination gaps to make the program reliably agent-ready.