AgentsReady
Readiness index · #411 of 1846

socket.dev

Run the agent liveReport a change
57Readiness score / 100
L2 Agent-documentedBeats 77% of 1,846 companies
Access10/20
Context11/20
Interfaces28/32
Onboarding3/19
Trust5/9
llms.txt · root
MCP · https://mcp.socket.dev/
OpenAPI · https://api.socket.dev/v1/openapi.json

Biggest gains

  1. +10 Agents get the real page, not a bot wall. Serve the homepage to AI user-agents (Claude-User, ChatGPT-User) without a challenge or 403.
  2. +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
  3. +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
All 20 checks
  • FAILAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • FAILDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • FAILPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • FAILOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • PASSsecurity.txt2
  • PASSPublic status page3

Your fix pack: 9 changes, up to +43 points

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

Your homepage returned a challenge or 403 to a Claude-User agent. Agents acting for a person give up and pick a competitor.

Where: Your WAF or bot-management rules (Cloudflare, Akamai, Vercel Firewall, AWS WAF)
Cloudflare: Security > WAF > Custom rules > Create rule
  Name: Allow user-triggered AI agents
  Expression:
    (http.user_agent contains "Claude-User") or (http.user_agent contains "ChatGPT-User")
    or (http.user_agent contains "Perplexity-User") or (http.user_agent contains "OAI-SearchBot")
    or (http.user_agent contains "Claude-SearchBot")
  Action: Skip > All remaining custom rules, Super Bot Fight Mode, Browser Integrity Check

Also in Security > Bots: turn on "Allow verified bots".
Keep rate limits on; only the challenge page is the problem.
Check it worked:curl -s -o /dev/null -w "%{http_code}\n" -A "Claude-User/1.0" https://socket.dev/ # expect 200

Add the badge to your README

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