Agent readiness · Embeddable rich text editors
froala.com
5 of 9 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. 5 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) across three tries (403, 200, 200)
- PASSllms.txt publishedllms.txt present at https://froala.com/llms.txt, and the 12 links we sampled across the file all answer
- UNMEASUREDDocs readable without JavaScriptUnmeasurable: no documentation page could be found to readLink your documentation from your home page or list it in llms.txt.
- 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
- UNMEASUREDAgent entry pointUnmeasurable: 3 of the 9 known agent entry paths answered with a refusal rather than a file or a 404, so what you publish there is not something we measuredLet ordinary HTTP reach these paths and this becomes measurable.
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
- FAILMCP surfaceNo MCP surface: nothing answered at mcp.froala.com, mcp.froala.com/mcp, mcp.froala.com/v1/mcp, api.froala.com/mcp, /mcp or /api/mcp, and no file mentions MCP
C · Registration
- FAILNo CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML, even though the form itself is assembled by JavaScript
- UNMEASUREDSignup reachable without a browserUnmeasurable: https://froala.com/signup answers 404 to an agent and 403 to a Chrome user-agent, so nothing gets in from here and the difference we test for cannot be seenNothing for you to do here. It becomes measurable from a network your edge admits.
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.
- UNMEASUREDFree tier or no-card trial stated in textUnmeasurable: no pricing page could be fetchedLink a pricing page from your home page, or list one in llms.txt.
E · Integration
- PASSTyped SDK on the registryfroala-editor@5.3.1 ships types
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://froala.com, 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 froala.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.