Agent readiness · Documents and e-signature
youtrust.com
Your edge challenged us
developers.youtrust.com answered 15 of the 15 requests it refused with a browser challenge rather than a rate limit. A browser passes one of those invisibly and an HTTP client cannot pass it at all, which is the difference this scorecard is about. It costs no points: wherever that stopped us, the check says so and is marked unmeasurable rather than failed. What it costs is a row thinner than your product deserves, and an agent that stops where we stopped.
5 of 11 measurable points under formula 9.57, measured on 2026-09-03. 16 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/bot)
- FAILPrice or entry condition in the search snippetYour pricing page's description tag names no amount and no entry condition: “Youtrust API pricing: find the right plan for your needs and integrate Youtrust's eSignature API.”Put the number, or the entry condition in words ("free tier", "no credit card"), into the pricing page's meta description. That string is what an agent reads when it decides whether to open you at all.
- PASSllms.txt publishedllms.txt present at https://youtrust.com/llms.txt and https://developers.youtrust.com/llms.txt, and the 12 links we sampled across both files all answer
- PASSDocs readable without JavaScript1,623 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 23 agent entry paths we asked on your site and your documentation host returns a file rather than your page shell
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed: https://youtrust.com, https://id.youtrust.com, https://oauth.youtrust.com, https://api.youtrust.com, and 5 more
- FAILMCP surfaceNo MCP surface: nothing spoke MCP at mcp.youtrust.com, mcp.youtrust.com/mcp, mcp.youtrust.com/v1/mcp, api.youtrust.com/mcp, api.youtrust.com/v1/mcp, /mcp or /api/mcp, and any address you publish in the MCP registry, and no file mentions MCP
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: we found no link to an account signup in the served HTML of https://youtrust.com, https://youtrust.com/pricing-api, https://developers.youtrust.com, while you publish prices at https://youtrust.com/pricing-api, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
- UNMEASUREDSignup reachable without a browserUnmeasurable: we found no link to an account signup in the served HTML of https://youtrust.com, https://youtrust.com/pricing-api, https://developers.youtrust.com, while you publish prices at https://youtrust.com/pricing-api, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
D · Provisioning
- UNMEASUREDProgrammatic key provisioningUnmeasurable: 1 documentation page we selected did not answer (429, and developers.youtrust.com answered 15 of the 15 requests it refused with a browser challenge rather than a limit, which is not a burst that passes), so nothing here is a finding about what you documentLet ordinary HTTP reach your documentation pages and this becomes measurable.
- UNMEASUREDFree tier or no-card trial stated in textUnmeasurable: https://youtrust.com/pricing-api is larger than we read, so anything we did not find in it is a fact about our cap and not about your tiersNothing for you to do. A smaller pricing page, or one that states its tiers early, makes this measurable.
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.
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths on your site or on your documentation host, none declared by https://developers.youtrust.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.
Free while we are building this, and we will ask before it ever costs anything. No card, no account, and one link in every email that stops it.
This page is the newest scan we hold for youtrust.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.
If a line here is wrong, rescan it first, because most of what we get told is already fixed and the page is only as new as the last scan. If it is still wrong after that, write to hello@letagentsin.com with the check and what you see instead. A verdict we cannot reproduce comes down, and the rule that produced it gets fixed for everybody rather than only for you.