AgentsReady
Readiness index · #143 of 1846

semgrep.dev

Run the agent liveReport a change
75Readiness score / 100
L3 Agent-operableBeats 92% of 1,846 companies
Access20/20
Context17/20
Interfaces24/32
Onboarding8/19
Trust6/9
llms.txt · root
MCP · https://docs.semgrep.dev/mcp

Biggest gains

  1. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  2. +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.
  3. +5 OAuth discovery metadata. Publish RFC 8414 authorization-server and RFC 9728 protected-resource metadata.
All 20 checks
  • PASSAgents 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
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-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
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 6 changes, up to +25 points

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

An OpenAPI spec is the contract agents and SDK generators build against. Without it they guess from prose.

Where: https://semgrep.dev/openapi.json, linked from llms.txt and the API reference
// Serve the spec your API framework already generates (FastAPI: /openapi.json is built in).
// Next.js: app/openapi.json/route.ts
import spec from "@/openapi/openapi.json";
export const GET = () => Response.json(spec, { headers: { "Access-Control-Allow-Origin": "*" } });

// Every operation needs: operationId, summary, description, request/response examples,
// and the auth scheme (components.securitySchemes) so agents know how to send the key.
Check it worked:curl -s https://semgrep.dev/openapi.json | head -c 200

Add the badge to your README

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