# Clearme — API Agent Score

> Score: 55/100 (Grade: D) | Domain: clearme.com | Rubric: 1.0.0 | Checked: July 29, 2026

Clearme scored 55/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 68/100 (C)
- Developer Experience: 56/100 (D)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 54/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Security & governance hygiene — security.txt valid at https://clearme.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [fail] Example coverage — No detectable code samples across 2 sampled docs pages. Investigated: docs 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — 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://www.clearme.com/clear-mobile; 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 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — Could not test any pages; 1 failed to fetch. Investigated: docs 60%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 1 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 — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [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 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Clearme's API program shows promise in discoverability but is held back by two critical gaps: partners and their AI agents lack the runnable, example-rich context needed to integrate quickly and correctly, and the documentation surface is neither structured nor agent-readable. Prioritize making the API immediately executable with realistic examples and test scripts, then layer in agent-oriented context (instructions, structured data, quickstart, and code samples) so partners — human and automated — can go from discovery to a working integration without friction.