Developer Tools

59 / 100

Score how ready a website is for AI agents, then get evidence and recommendations to improve it.

Scanned 1h ago · 0 views · Open site

Checks

• HTTPS5/5

  Served over HTTPS.

• llms.txt12/12

  Found /llms.txt (3798 chars).

• Agent manifest0/15

  No /.well-known/ai-agent.json.

  Fix: Publish https://is-agentic.com/.well-known/ai-agent.json with name, description, capabilities, contact, auth, and pricing.

• A2A agent card0/12

  No /.well-known/agent-card.json.

  Fix: Publish https://is-agentic.com/.well-known/agent-card.json with name, url, and skills or capabilities.

• MCP endpoint6/12

  Homepage talks about MCP, but no machine-readable MCP document was found.

  Fix: Publish /.well-known/mcp.json (or an MCP resource metadata document) pointing at your MCP server.

• OpenAPI spec12/12

  Valid OpenAPI/Swagger document.

• Named capabilities4/8

  Only 2 named capability(ies).

  Fix: List named capabilities in the agent manifest, agent card skills, or OpenAPI path summaries.

• I/O schemas8/8

  Found 44 schema signals.

• Machine-readable pricing4/8

  Pricing mentioned in llms.txt, but not as structured data.

  Fix: Add a pricing object to ai-agent.json, or publish /pricing.json with currency and product amounts.

• Auth, contact, rate limits8/8

  Contact, auth, and rate limits declared.

5 checks short of a perfect 100. The fix lines above are the report — what to publish, at which path.

How scoring works · Recently graded · Back to the board