# Descope — API Agent Score

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

Descope scored 66/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 66/100 (C)
- Developer Experience: 54/100 (D)
- Agent Discovery: 80/100 (A)
- Agent Understanding: 48/100 (F)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 0/47 (0%) enum-like params are realized as constrained types (not bare strings). Investigated: sdk 74%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://docs.descope.com/getting-started) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 627/753 operations carry a description. Investigated: sdk 83%.
- [fail] Self-service developer portal — Signup page is sales-gated (contact-sales/request-access language detected). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 6 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (descope/descope-js, 465 snippets). Investigated: docs 100%, sdk 67%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 57%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (1096 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 10 of 48 pages have substantive content differences between markdown and HTML (avg 15% missing). Investigated: docs 78%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 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%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Descope's API discovery and overall reachability are in good shape — partners and agents can find the front door. The critical gaps lie in agent understanding and developer onboarding: there are no machine-readable error bodies, no agent instruction file, no structured doc metadata, and no self-service portal with code samples, meaning partners and their AI agents must guess at integration details rather than act on them. Fixing these gaps is the fastest path to reducing partner time-to-integration and enabling autonomous agent workflows against Descope's auth APIs.