# Twitter — API Agent Score

> Score: 54/100 (Grade: D) | Domain: twitter.com | Rubric: 1.0.0 | Checked: July 21, 2026

Twitter scored 54/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 43/100 (F)
- Developer Experience: 61/100 (C)
- Agent Discovery: 100/100 (A+)
- Agent Understanding: 53/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt present but missing or expired Expires. Investigated: wellknown 50%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Example coverage — No detectable code samples across 20 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 — Self-service signup at https://x.com/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 143 day(s) ago. Investigated: sdk 100%.
- [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 20 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://docs.x.com/llms-full.txt. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (fa0311/twitter-openapi, 9 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Docs structured data — JSON-LD Article markup on 8/8 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 5% (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.
- [skip] Agent-navigable, token-efficient docs — 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

Twitter's API program shows meaningful strengths in auth and security, but partners and their AI agents face critical friction in two areas: the API contract is too thin to build against reliably (missing schema depth and real-world examples), and there is no runnable, agent-readable layer to accelerate integration. Fixing the contract quality and adding executable, discoverable context should be the immediate priority — together they determine whether partners can get to a working integration at all, and whether their coding agents can do it without guessing.
