The SDK agents will install for you was last published 19 months ago.

quill@2.0.3 last published 2025-01-20, still 10,850,551 downloads a week.

5/ 10

A dashed column is a stage we could not measure, not a stage you failed.

A · Discovery: 4/5
B · Agent entry: 0/3
C · Registration: n/m
D · Provisioning: n/m
E · Integration: 1/2

of the 10 points that apply to you and we could measure · 7 of 17 were not scored

You 5 · category median 5.5 · best liveblocks.io 8 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+4points, taking 5/10 to 9/10, past liveblocks.io, tiny.cloud, slatejs.org

This is the whole list: everything we could measure and you do not pass. Another 7 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

1
llms.txt publishedminutes · +1
Publish /llms.txt: a markdown list linking your quickstart, API reference, pricing and package name. It is the cheapest file on this list.
2
Agent entry pointan afternoon · +2
Publish /agent-signup.md: the path from nothing to a working key, written as steps for a machine rather than a tour for a person. Ours is at /agent-signup.md if you want a worked example, and it says plainly that we have nothing to sign up for.
3
Machine-readable API descriptionan afternoon · +1
Publish an OpenAPI file at /openapi.json, or serve markdown when a client sends Accept: text/markdown. Either one stops agents guessing your API.

Then, when you have room

OAuth dynamic client registration a project · +1Publish OAuth authorization server metadata with an RFC 7591 registration_endpoint in it. It is the only standard way an agent registers itself without a human.

Take it with you

8 of the checks an agent depends on, quilljs.com does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on quilljs.com. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Read the audits in full What the same run on quilljs.com costs

Against embeddable rich text editors

You are 6 of 10 in a category where a developer is trying to put a real editor inside a product.

1
liveblocks.io
8/14
2
ckeditor.com
9/16
3
tiptap.dev
9/16
4
froala.com
5/9
5
tiny.cloud
8/15
6
quilljs.comyou
5/10
7
slatejs.org
6/13
8
editorjs.io
4/10
9
lexical.dev
4/10
10
prosemirror.net
4/11

Where competitors pass and quilljs.com does not

llms.txt publishedckeditor.com · tiny.cloud · tiptap.dev · froala.com · liveblocks.io
Free tier or no-card trial stated in textckeditor.com · tiny.cloud · tiptap.dev · liveblocks.io
Machine-readable API descriptionckeditor.com · tiptap.dev · slatejs.org · liveblocks.io
Signup reachable without a browserckeditor.com · tiptap.dev

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

DiscoveryCan an agent find and read you?

4/5

Agent entryIs there a door built for a machine?

0/3

RegistrationCan an agent get an account?

not measured

ProvisioningCan it get credentials without a human?

not measured

IntegrationCan it ship working code?

1/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

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 probedA curated map of your docs is the cheapest way to control what an agent reads first. Worth one point and not more: in eighteen isolated agent runs across four categories, not one cited llms.txt among its sources, and an independent ninety-day measurement published by Otterly in February 2026 found it served 84 requests against 62,100 AI-bot visits.
PASS
Docs readable without JavaScript2,041 characters of text without JS
PASS
On-demand agents not blockedNo on-demand agent is blocked
N/A
Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
PASS
No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

FAIL
Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shellA markdown file written for a machine turns a guessing game into a procedure it can follow.
FAIL
OAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomainsRFC 7591 is the only standard path by which an agent can register itself without a human.
UNMEASURED
MCP 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/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 registryquill@2.0.3 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://quilljs.com/docs/quickstart, and no markdown negotiationAn OpenAPI file or markdown negotiation lets an agent read your API instead of guessing it.Point at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

What we discovered on the way

Docs: https://quilljs.com/docs/quickstart · linked from the site
Pricing: not found
Signup: not found
npm package: quill (registry guess)
GitHub: slab/quill
Package licence: BSD-3-Clause
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none