# Clear — API Agent Score

> Score: 59/100 (Grade: D) | Domain: clear.me | Rubric: 1.0.0 | Checked: July 29, 2026

Clear scored 59/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 59/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 56/100 (D)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 53/100 (D)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — 1/1 enums are named types (not bare strings). Investigated: sdk 100%.
- [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] Self-service developer portal — Signup page at https://app.backgroundchecks.com/new-order; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [warn] Changelog published — Newest official SDK activity 203 days ago — drifting from the contract. Investigated: sdk 50%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 2 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/clearme, 745 snippets). Investigated: docs 100%, sdk 67%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 86%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 50 JavaScript redirect(s) detected across 50 sampled pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 50 pages exceed 100K chars (max 117K). Investigated: docs 65%.
- [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 2 assessed pages (2 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [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

Clear's API program shows solid discovery foundations, but two areas are holding back partner and agent adoption: Agent Understanding is critically weak — agents lack the structured context and instruction files needed to parse and act on your APIs without guesswork — and Agent Usability is failing, with no runnable collection or idempotency documentation to give partners and their tools a reliable path to production. Prioritize making your API surface agent-readable and executable first, then close the onboarding gaps (quickstart, code samples) that slow human partners from their first successful call.