DEVELOPERS

CLI and scan API

Install the CLI and start a scan from the command line. Use the API to start scans, poll the returned URL, and read the completed canonical report.

npm install -g @isagentready/cli npx @isagentready/cli scan example.com

OpenAPI: The OpenAPI specification documents requests and responses. Completed report fields are additive and versioned by methodology.

MCP and A2A

Connect Streamable HTTP MCP clients to /mcp. The endpoint supports stateless MCP 2026-07-28 and the existing handshake. Report tools return identical JSON in the text fallback and structuredContent. The fixed ui://isagentready/score-report.html resource renders the scorecard without external assets. Discover capabilities through /.well-known/mcp.json and use the A2A Agent Card for task-based integrations.

Agent Skills are listed at /.well-known/agent-skills/index.json.

Rate limits and errors

Responses limited by quota include RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and Retry-After. Reuse cached results before requesting another scan.

API errors use problem details with type, title, status, detail, and instance, while retaining legacy error and message fields.

Compatibility

Public reports keep their stored methodology version. New report fields are additive, and deprecated integrations remain documented until a replacement is available.

Monitoring APIs require verified ownership and a management bearer token. Public scan, rankings, MCP, and A2A reads remain credential-free.

A2A retains its protocol-specific application/a2a+json errors; the JSON API uses problem details.