Agent readiness · Embeddable rich text editors
tiny.cloud
8 of 15 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
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://www.tiny.cloud/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript16,939 characters of text without JS, on https://www.tiny.cloud/docs/tinymce/7/invalid-api-key/ rather than on https://www.tiny.cloud/docs/tinymce/latest/
- 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
- PASSOAuth dynamic client registrationregistration_endpoint published, and client_credentials is among the 13 advertised grants, so an unattended agent has a documented path to a token
- FAILMCP surfaceNo MCP surface: nothing answered at mcp.tiny.cloud, mcp.tiny.cloud/mcp, mcp.tiny.cloud/v1/mcp, api.tiny.cloud/mcp, /mcp or /api/mcp, and no file mentions MCP
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://www.tiny.cloud/auth/signup/ is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://www.tiny.cloud/auth/signup/ is reachable, but its form needs JavaScript
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 5 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://www.tiny.cloud/pricing/: "Free Trial", "$0"
E · Integration
- PASSTyped SDK on the registrytinymce@8.8.2 ships types
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://www.tiny.cloud/docs/tinymce/latest/, 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 tiny.cloud 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.