# Atlassian — API Agent Score

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

Atlassian scored 68/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 84/100 (A)
- Developer Experience: 75/100 (B)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 69/100 (C)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → lib/index. Investigated: sdk 100%, spec 47%.
- [warn] Machine-readable, versioned contract — info.version="1001.0.0-SNAPSHOT-b5920d1eaef179a2bd7f107d8da95822cab568b5" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Auth declared & discoverable — 1 OAuth2/OIDC scheme(s) defined but no scopes documented. Investigated: spec 70%, docs 60%, wellknown 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.atlassian.com/; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 96% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 10 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (3 variants scanned starting at https://developer.atlassian.com/?utm_source=%2Fgetting-started&utm_medium=301) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 9 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_atlassian_platform_forge, 10616 snippets). Investigated: docs 100%, cli 100%, mcp 100%, sdk 67%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 15 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.atlassian.com/llms.txt, https://developer.atlassian.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (65 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 8 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [warn] Operation purpose clarity — 31% of operations are agent-inferable. Investigated: spec 80%.
- [warn] Agent-navigable, token-efficient docs — 3 of 50 sampled pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. Investigated: docs 56%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 4% (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 1 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Pagination documented & consistent — pagination documented in the docs site at https://www.atlassian.com/software/jira/dev. Investigated: docs 100%, spec 75%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [warn] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 20%, docs 20%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 0%.

## Executive Summary

Atlassian's API design is a clear strength — the contract is machine-readable, well-shaped, and auth is properly covered — giving partners a solid foundation to build on. The critical gaps are in agent understanding and agent usability: there is no AGENTS.md instruction file, no structured data in docs, and no idempotency guidance, leaving AI agents without the context they need to integrate safely and autonomously. The highest-leverage priority is closing the agent-understanding layer first (machine-readable docs, agent instructions, structured context), then making the API surface executable and trustworthy for partner workflows.