# Facebook — API Agent Score

> Score: 77/100 (Grade: B) | Domain: facebook.com | Rubric: 1.0.0 | Checked: July 29, 2026

Facebook scored 77/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 75/100 (B)
- Agent Discovery: 77/100 (B)
- Agent Understanding: 80/100 (A)
- Agent Usability: 63/100 (C)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — Medium parameter complexity (avg 4.5 params/op; nested/body schemas present). Investigated: spec 83%, sdk 44%.
- [warn] Machine-readable, versioned contract — info.version="v23.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — 96% example coverage across params + responses. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://developers.meta.com/newsletter/; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 90% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — Newest official SDK activity 2 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://business.facebook.com/business/loginpage/?next=https%3A%2F%2Fdevelopers.facebook.com%2Fquickstarts%2F) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 8 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (kevinzg/facebook-scraper, 497 snippets). Investigated: docs 100%, cli 100%, sdk 67%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 80%, sdk 0%.
- [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

- [pass] Machine-readable errors (RFC 9457) — 8 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 98% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 81%.
- [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 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 27 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Rate-limit signaling — Only 1 rate-limit header(s) documented. Investigated: spec 50%, docs 50%.
- [fail] Idempotency documented — 2% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Facebook's API program shows strong API design fundamentals and good discovery foundations, but partners and their AI agents face two critical gaps: there is no structured context layer to help agents understand how to work with the APIs, and there is no runnable, executable truth for agents to build reliable integrations against. Closing these gaps — by publishing agent-readable instructions and structured documentation, then providing executable collections with test coverage and idempotency guidance — should be the immediate priority to unlock self-serve partner success at scale.