Other

5 / 100

Merge is the infrastructure layer for production AI. One platform connects your products and agents to every API, tool, and LLM they need to run at scale.

Scanned 1h ago · 1 views · Open site

Checks

• HTTPS5/5

  Served over HTTPS.

• llms.txt0/12

  No /llms.txt.

  Fix: Publish https://merge.dev/llms.txt with a short description, key URLs, and how an agent should call you.

• Agent manifest0/15

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

  Fix: Publish https://merge.dev/.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://merge.dev/.well-known/agent-card.json with name, url, and skills or capabilities.

• MCP endpoint0/12

  No MCP document or endpoint found.

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

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

  No named capabilities, skills, or API operations.

  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 pricing0/8

  No machine-readable pricing.

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

• Auth, contact, rate limits0/8

  No contact, auth, or rate limit declaration.

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

9 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