Let Agents In

Agent readiness · Embeddable rich text editors

prosemirror.net

4 of 11 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 1 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.

A · Discovery

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • FAIL
    llms.txt publishedNo llms.txt at any of the 4 locations probed
  • FAIL
    Docs readable without JavaScriptOnly 647 characters render without JS
  • PASS
    On-demand agents not blockedNo robots.txt, so nothing is disallowed for anyone
  • N/A
    Paths robots.txt points at answerNo robots.txt, so it points nowhere
  • PASS
    No punishing crawl delayNo robots.txt, so no Crawl-delay applies

B · Agent entry

  • FAIL
    Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
  • FAIL
    OAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
  • FAIL
    MCP surfaceNo MCP surface: nothing answered at mcp.prosemirror.net, mcp.prosemirror.net/mcp, mcp.prosemirror.net/v1/mcp, api.prosemirror.net/mcp, /mcp or /api/mcp, and no file mentions MCP

C · Registration

  • N/A
    No CAPTCHA in the signup HTMLNot applicable: nothing on the site links to pricing or to an account signup, so there is no gate to measureIf accounts are created somewhere else, tell us where and we will rescan.
  • N/A
    Signup reachable without a browserNot applicable: nothing on the site links to pricing or to an account signupA product with no accounts cannot fail this. If yours has them elsewhere, point us at the page.

D · Provisioning

  • UNMEASURED
    Programmatic key provisioningUnmeasurable: only 1 documentation page could be read, which is too little to conclude anythingLink your API reference from your docs index or from llms.txt and this becomes measurable.
  • N/A
    Free tier or no-card trial stated in textNot applicable: nothing on the site links to pricing or to an account, so there is no tier to stateIf there is a paid tier, link its pricing from your home page and we will rescan.

E · Integration

  • PASS
    Typed SDK on the registryprosemirror-view@1.42.2 ships types, matched from the registry by who publishes it rather than by a link on your site
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://prosemirror.net/docs/, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

Tell me when this changes

The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.

This page is the newest scan we hold for prosemirror.net and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.

Scan a domain yourself