New64 developer platforms, traced by hand: how long it takes an agent to get an API keySee the benchmark →
AgentsReady
Readiness index · #897 of 1846

twitter.com

Run the agent liveReport a change
37Readiness score / 100
L1 Agent-readableBeats 50% of 1,846 companies
Access10/20
Context2/20
Interfaces20/32
Onboarding5/19
Trust0/9
MCP · https://api.twitter.com/mcp

Biggest gains

  1. +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
  2. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  3. +6 robots.txt lets user-triggered agents in. Don't Disallow ChatGPT-User, Claude-User or Perplexity-User. Block training crawlers separately if you must.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • FAILrobots.txt lets user-triggered agents in6
  • FAILContent is server-rendered4
  • FAILllms.txt exists8
  • FAILllms-full.txt exists3
  • FAILDocs available as markdown6
  • PASSSitemap2
  • FAILStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • FAILSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • FAILFree tier or test mode3
  • FAILAgent manifests4
  • FAILsecurity.txt2
  • FAILPublic status page3

Your fix pack: 15 changes, up to +63 points

Each change is ready to paste, filled in for twitter.com, with a command to check it worked. Or hand the whole list to your coding agent.

llms.txt is the first file an agent looks for. It tells it what you do and where every doc lives, in one cheap request.

Where: https://twitter.com/llms.txt (and https://docs.twitter.com/llms.txt)
# Twitter

> One sentence: what Twitter does and who it's for.

Twitter offers <products>. Use the API to <core jobs>. Get a test key in under a minute at <signup or dashboard URL>.

## Start here
- [Quickstart](https://docs.twitter.com): first API call in 5 minutes
- [Authentication and API keys](https://docs.twitter.com/authentication): how to get and scope a key
- [Pricing and limits](https://twitter.com/pricing): free tier, rate limits, what each call costs

## Build
- [API reference](https://docs.twitter.com/api-reference)
- [OpenAPI spec](https://twitter.com/openapi.json)
- [MCP server](https://docs.twitter.com/mcp): https://api.twitter.com/mcp
- [SDKs](https://docs.twitter.com/sdks): TypeScript, Python
- [Errors](https://docs.twitter.com/errors)

## Optional
- [Changelog](https://docs.twitter.com/changelog)
- [Status](https://status.twitter.com)
Check it worked:curl -s https://twitter.com/llms.txt | head -3 # first line should start with "# "

Want the full treatment, not just these fixes? Get the prompt that takes your coding agent through every phase.

Add the badge to your README

AgentsReady badge for twitter.com
[![AgentsReady](https://agentsready.dev/badge/twitter.com)](https://agentsready.dev/c/twitter.com)