# Auth0 — API Agent Score

> Score: 85/100 (Grade: A) | Domain: auth0.com | Rubric: 1.0.0 | Checked: July 24, 2026

Auth0 scored 85/100 (A), classified "ai-ready".

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

## Summary

- Overall: 85/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 91/100 (A+)
- Agent Discovery: 92/100 (A+)
- Agent Understanding: 78/100 (B)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 1 of 34 public signatures use loose types (anyTypeRatio=0.029). Investigated: sdk 92%.
- [pass] Security & governance hygiene — security.txt valid at https://auth0.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [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] Self-service developer portal — Self-service signup at https://auth0.com/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [warn] Description completeness — 5/17 operations lack a description. Investigated: sdk 71%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://auth0.com/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/auth0, 37739 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] Crawlable / AEO — Sitemap present (9 entries) but carries no lastmod values. Investigated: wellknown 50%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "GenericError" with 8 subclasses. Investigated: sdk 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — 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%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [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

Auth0's API program is already strong on design clarity and developer experience, giving partners a solid foundation to evaluate and build against the platform. However, two gaps stand out as the most consequential for partner and agent success: AI agents lack a structured instructions file to understand how to interact with Auth0's APIs, and there are no runnable collections with test scripts to give partners and their coding agents verified, executable workflows. Closing these two gaps — in that order — will meaningfully accelerate partner integration quality and reduce the support burden that comes from agents and developers guessing at correct usage patterns.