Your signup page answers 429 to anything that is not a browser.

https://dashboard-v3.nylas.com/register returned 429 across three tries. An agent that got this far still cannot open an account.

9/ 14

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

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

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

You 9 · category median 8.5 · best cal.com 10 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+3points, taking 9/14 to 12/14, past cal.com

This is the whole list: everything we could measure and you do not pass. Another 3 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
Your llms.txt is already there. 1 of the 12 links we sampled are gone, starting with https://www.nylas.com/products/express-security-review-old/. Fix those and this passes: a map an agent follows into a 404 costs it the budget it came with.
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.

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.
MCP surface a project · +1You already talk about MCP, and nothing answered at the addresses named above. If your server is at another path, declare it at /.well-known/mcp.json: that file is what an agent reads first, and it is what makes the path stop mattering.

Take it with you

5 of the checks an agent depends on, nylas.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 nylas.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 nylas.com costs

Against scheduling and calendar apis

You are 2 of 6 in a category where a developer is trying to book a meeting into a calendar you do not control.

1
cal.com
10/15
2
nylas.comyou
9/14
3
calendly.com
9/15
4
savvycal.com
8/16
5
timekit.io
7/14
6
cronofy.com
6/15

Where competitors pass and nylas.com does not

OAuth dynamic client registrationcal.com · calendly.com · savvycal.com
MCP surfacecal.com · calendly.com · savvycal.com
llms.txt publishedcal.com · timekit.io
Paths robots.txt points at answercalendly.com

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/4

RegistrationCan an agent get an account?

not measured

ProvisioningCan it get credentials without a human?

3/3

IntegrationCan it ship working code?

2/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 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/A 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 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/
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 9 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.
FAIL
MCP 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/mcpAn MCP server turns your API from something an agent reads about into something it can call.

C · Registration

UNMEASURED
No 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.
UNMEASURED
Signup 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

PASS
Programmatic key provisioning2 of 7 provisioning phrases across the 7 documents we read: "management api", "service account"
PASS
Free 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

PASS
Typed 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
PASS
Machine-readable API descriptionOpenAPI at https://developer.nylas.com/_spec-files/nylas-api.yaml, which your docs page declares with rel="service-desc"

What we discovered on the way

Docs: https://developer.nylas.com/ · linked from the site
Pricing: https://www.nylas.com/pricing/ · linked from the site
Signup: https://dashboard-v3.nylas.com/register · linked from the site
npm package: nylas (registry guess)
GitHub: nylas/cli
Package licence: MIT
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none