# Clearbit — API Agent Score

> Score: 47/100 (Grade: F) | Domain: clearbit.com | Rubric: 1.0.0 | Checked: July 24, 2026

Clearbit scored 47/100 (F), classified "not-ai-ready".

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

## Summary

- Overall: 47/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 60/100 (C)
- Agent Discovery: 62/100 (C)
- Agent Understanding: 51/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [fail] Example coverage — No detectable code samples across 10 sampled docs pages. Investigated: docs 0%, sdk 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.clearbit.com/auth/signup?flow=data_test; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://app.clearbit.com/auth/login) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 10 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 587 days ago. Investigated: sdk 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 6 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 3 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap present (500 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://clearbit.com/docs/llms.txt, https://clearbit.com/llms.txt); candidates redirected cross-host to https://dashboard.clearbit.com (agents can't follow cross-host redirects). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 22 of 50 sampled pages appear to be client-side rendered SPA shells (__next detected); agents using HTTP fetches will see no content. Investigated: docs 43%.
- [warn] Docs structured data — OpenGraph/meta tags only across 4 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 8% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 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.

### 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

Clearbit's API program shows meaningful strengths in documentation reachability and parseability, but three areas are putting partner outcomes at serious risk: the API contract itself lacks the schema depth, security clarity, and realistic examples that partners and their AI agents need to build confidently; agents have no structured instructions or discovery artifacts to navigate the API without human intervention; and there is no runnable, testable collection for partners to validate integrations against. Fixing the contract quality and agent-readiness surface should be the immediate priority, followed by closing the discoverability and changelog gaps that slow partners from finding and trusting what has changed.