Agent readiness · Embeddable rich text editors
quilljs.com
5 of 10 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. 2 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
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- FAILllms.txt publishedNo llms.txt at any of the 4 locations probed
- PASSDocs readable without JavaScript2,041 characters of text without JS
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
- UNMEASUREDMCP surfaceUnmeasurable: every JSON-RPC POST we sent came back with an empty 2xx, including one to a path nobody registered, so what answered was your edge rather than your serverNothing for you to do if your server is reachable from other networks. Whether an MCP server is there becomes measurable from a network your edge does not intercept.
C · Registration
- N/ANo 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/ASignup 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
- UNMEASUREDProgrammatic 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/AFree 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
- PASSTyped SDK on the registryquill@2.0.3 ships types, matched from the registry by who publishes it rather than by a link on your site
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://quilljs.com/docs/quickstart, 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 quilljs.com 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.