Skip to content
Farm.js v0.1.0 is releasedRead the announcement
Agent-ready check

Is your site ready for agents?
Find out in seconds.

One address in, a score out, and a concrete fix for every gap. Works for any site, whatever it's built with.

What it checks

Ten checks.
One score.

Every check looks at what an agent sees without a browser: the HTML, the Markdown, the discovery files, and the tools a site offers. Scores add up to 100; drafts are reported but not scored.

  1. Readable without JavaScript

    Content in the HTML, not behind a sign-in or a client render.

    GET /20 pts
  2. Markdown version

    A .md URL and Accept: text/markdown, linked from the page.

    GET /index.md20 pts
  3. llms.txt

    A Markdown index of the site for language models.

    GET /llms.txt15 pts
  4. robots.txt

    Agents acting for users and AI search aren't blocked.

    GET /robots.txt15 pts
  5. Title, canonical, Open Graph

    How agents name and cite the page.

    <head>10 pts
  6. MCP server

    Tools agents can call over Streamable HTTP.

    POST /api/mcp10 pts
  7. OpenAPI

    A machine-readable description of the site's API.

    GET /openapi.json5 pts
  8. JSON-LD

    schema.org data about who runs the site.

    ld+json5 pts
  9. Agent card

    Reported, not scored, while the specs settle.

    /.well-knownNot scored
  10. WebMCP

    Tools the page registers for in-browser agents. Reported.

    modelContextNot scored
Then what

Readable is step one.

Farm.js apps answer most of these checks by default. The agent infrastructure we're building goes further: one gateway for your tools, and a trace of every agent run.