# Fern — API Agent Score

> Score: 71/100 (Grade: B) | Domain: fern.com | Rubric: 1.0.0 | Checked: July 30, 2026

Fern scored 71/100 (B), classified "partially-ready".

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

## Summary

- Overall: 71/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 72/100 (B)
- Developer Experience: 97/100 (A+)
- Agent Discovery: 87/100 (A)
- Agent Understanding: 61/100 (C)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — 107/107 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%.
- [warn] Machine-readable, versioned contract — `--help --format json` exits 0 but output is not JSON. Investigated: cli 75%.
- [warn] Auth declared & discoverable — help mentions auth but not the exact env var. Investigated: cli 50%.
- [pass] Example coverage — help shows a runnable example invocation. Investigated: cli 100%, sdk 50%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://dashboard.buildwithfern.com/sign-up?redirect_on_login=%2Fget-started&utm_source=fern-docs; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://buildwithfern.com/learn/docs/getting-started with a runnable first-call sample. Investigated: docs 100%.
- [warn] Description completeness — 20/23 operations carry a description. Investigated: sdk 87%.
- [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] Registry & SDK presence — Indexed on Context7 (fern-api/docs, 9135 snippets). Investigated: docs 100%, sdk 92%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 75%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 50 pages have substantive content differences between markdown and HTML (avg 1% missing). Investigated: docs 70%.
- [warn] Machine-readable errors (RFC 9457) — Single base error "null" present, but only 1 subclass found; a richer hierarchy lets consumers catch narrowly. Investigated: sdk 50%, cli 0%.
- [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] 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] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%, cli 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

Your developer experience and discoverability are standout strengths — partners can find and evaluate your APIs with minimal friction. However, two areas are holding back production-grade partner integrations: agents and developers lack the contextual instructions and runnable, test-backed examples they need to integrate confidently, and operational reliability gaps (missing idempotency guidance and security hygiene documentation) increase the risk of failed or unsafe partner workflows. Prioritize giving agents and partners executable, trustworthy context first, then close the operational documentation gaps to protect partners building real-world automations.