Agent readiness · Documents and e-signature
pdfmonkey.io
6 of 13 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. 3 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 publishedllms.txt and llms-full.txt present at https://pdfmonkey.io/llms.txt and https://pdfmonkey.io/llms-full.txt, but 2 of the 12 links we sampled across both files are gone, starting with https://pdfmonkey.io/docs/img/custom-style-panel.webp
- PASSDocs readable without JavaScript6,556 characters of text without JS, on https://pdfmonkey.io/docs/account-and-security/account-deletion/ rather than on https://pdfmonkey.io/docs/
- 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 9 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
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://dashboard.pdfmonkey.io/register 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://dashboard.pdfmonkey.io/register is reachable, but its form needs JavaScript
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://pdfmonkey.io/pricing/: "no credit card", "free tier", "free plan"
E · Integration
- UNMEASUREDTyped SDK on the registryUnmeasurable: we could not identify the package a developer installs to use you, from your site, your docs or a registry searchName your package once in your docs, or link it from your repository, and we stop guessing. If your product is not something a developer installs, this check does not apply to you: unmeasured is out of the score and out of the denominator, so it costs you nothing.
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://pdfmonkey.io/docs/api/authentication.md
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 pdfmonkey.io 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.