AI Agents

52 / 100

Tells other agents what phone calls call4me can make for a user and exactly what each kind of call needs before dialing. Placing the call itself goes through the call4me MCP server at https://call4.me

Scanned 3h ago · 0 views · Open site

Checks

• HTTPS5/5

  Served over HTTPS.

• llms.txt12/12

  Found /llms.txt (6746 chars).

• Agent manifest0/15

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

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

• A2A agent card12/12

  A2A agent card with skills or capabilities.

• MCP endpoint12/12

  Discoverable MCP metadata or endpoint.

• OpenAPI spec0/12

  No OpenAPI or Swagger spec found.

  Fix: Serve /openapi.json (or /swagger.json) with a valid OpenAPI spec, or link it from the homepage.

• 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 schemas0/8

  No I/O schemas.

  Fix: Add components.schemas / requestBody schemas in OpenAPI, or input/output schemas on each skill.

• 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 limits3/8

  Declared: auth.

  Fix: Declare contact, auth, and rateLimit in ai-agent.json (and OpenAPI info.contact / securitySchemes).

6 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