# Linear — API Agent Score

> Score: 67/100 (Grade: C) | Domain: linear.app | Rubric: 1.0.0 | Checked: July 24, 2026

Linear scored 67/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 84/100 (A)
- Developer Experience: 89/100 (A)
- Agent Discovery: 90/100 (A+)
- Agent Understanding: 58/100 (D)
- Agent Usability: 41/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 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [warn] Schema coverage & depth — Only 0% of operations have documented schemas. Investigated: spec 50%, sdk 0%.
- [pass] Example coverage — Code samples present on 4/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, spec 0%, sdk 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://linear.app/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 4/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://linear.app/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (8 variants scanned starting at https://linear.app/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.

### Agent Discovery

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

### Agent Understanding

- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 2 of 26 pages have substantive content differences between markdown and HTML (avg 10% missing). Investigated: docs 78%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 11% (threshold 35% for full credit).
- [fail] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 0%, docs 0%.
- [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%.

### Agent Usability

- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [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%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Linear's API design and developer onboarding are strong, and documentation discoverability is excellent — partners can find the API without friction. However, the program has critical gaps in how its APIs communicate with AI agents and how safely those agents can operate in real workflows. The highest-priority work is making errors, rate limits, idempotency, and agent-facing instructions machine-readable and actionable — without these, partners' AI agents will fail silently, retry incorrectly, and corrupt data in production. Closing these gaps is what separates a partner-ready API from one that blocks AI-native integrations.