Agent readiness · Scheduling and calendar APIs
nylas.com
9 of 14 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. 2 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://www.nylas.com/llms.txt and https://developer.nylas.com/llms.txt and https://developer.nylas.com/llms-full.txt, but 1 of the 12 links we sampled across both files are gone, starting with https://www.nylas.com/products/express-security-review-old/
- PASSDocs readable without JavaScript35,143 characters of text without JS, on https://developer.nylas.com/docs/v3/auth/hosted-oauth-apikey/ rather than on https://developer.nylas.com/
- 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
- FAILMCP surfaceMCP mentioned 12x in your own files, but nothing answered at mcp.nylas.com, mcp.nylas.com/mcp, mcp.nylas.com/v1/mcp, api.nylas.com/mcp, /mcp or /api/mcp
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://dashboard-v3.nylas.com/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.
- UNMEASUREDSignup reachable without a browserUnmeasurable: https://dashboard-v3.nylas.com/register answered 429, which is a limit we triggered rather than a rule about agentsNothing for you to do. We will rescan later and this becomes measurable.
D · Provisioning
- PASSProgrammatic key provisioning2 of 7 provisioning phrases across the 7 documents we read: "management api", "service account"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://www.nylas.com/pricing/: "no credit card", "free forever", "$0"
E · Integration
- PASSTyped SDK on the registrynylas@8.4.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionOpenAPI at https://developer.nylas.com/_spec-files/nylas-api.yaml, which your docs page declares with rel="service-desc"
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 nylas.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.