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
- +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
- +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.
Add the badge to your README
[](https://agentsready.dev/c/twitter.com)