---
title: "Docs Benchmark Report: developer.nylas.com"
description: "developer.nylas.com benchmark report with category scores and check-level detail."
canonical: "https://docsalot.dev/benchmarks/docs/developer-nylas-com"
human_url: "https://docsalot.dev/benchmarks/docs/developer-nylas-com"
markdown_url: "https://docsalot.dev/benchmarks/docs/developer-nylas-com.md"
index_url: "https://docsalot.dev/benchmarks/docs"
index_markdown_url: "https://docsalot.dev/benchmarks/docs.md"
updated: "2026-11-02"
---

[Back to docs benchmark index](https://docsalot.dev/benchmarks/docs.md)

# Docs Benchmark Report: developer.nylas.com

> Copy this markdown report into a developer ticket or coding agent prompt when you want concrete docs fixes tied to benchmark checks.

## Report Links

- Human report: https://docsalot.dev/benchmarks/docs/developer-nylas-com
- Markdown report: https://docsalot.dev/benchmarks/docs/developer-nylas-com.md
- Benchmark index: https://docsalot.dev/benchmarks/docs
- Benchmark index markdown: https://docsalot.dev/benchmarks/docs.md
- Public docs URL: https://developer.nylas.com/

## Score Summary

- Report for: developer.nylas.com
- Display URL: developer.nylas.com
- Report type: Public benchmark report
- Score: 105
- Grade: Excellent
- Summary: Agents should be able to find the right page, fetch the content, and follow the instructions without much extra guesswork.
- Checked at: November 2, 2026 at 6:36 PM UTC
- Category: DocsAlot runs
- Source: DocsAlot run
- Checks passed: 17/17
- Warnings: 0
- Failed checks: 0
- Skipped checks: 0

## What Already Works

- LLMS TXT exists
- Markdown parity exists
- LLMS TXT is structured

## What To Improve Next

- None listed.

## Full Score Breakdown

### Discovery and delivery - 100/100

- Question: Can an agent find the docs and fetch readable text?
- Category focus: Entry points, markdown access, and machine-readable delivery
- Category note: This area is already easy for agents to work through.
- Passed: 3
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - LLMS TXT exists: Found llms.txt at https://developer.nylas.com/llms.txt (95818 chars)
- PASS - LLMS Full exists: Found llms-full.txt at https://developer.nylas.com/llms-full.txt (9097630 chars)
- PASS - Markdown parity exists: 5/5 sampled pages have valid .md versions. Pages sourced from llms.txt. Checked: ✓ https://developer.nylas.com/docs/v3/getting-started/index.html.md, ✓ https://developer.nylas.com/docs/v3/getting-started/dashboard/index.html.md, ✓ https://developer.nylas.com/docs/v3/getting-started/cli/index.html.md, ✓ https://developer.nylas.com/docs/v3/getting-started/coding-agents/index.html.md, ✓ https://developer.nylas.com/docs/v3/getting-started/email/index.html.md

### Content structure - 100/100

- Question: Can an agent understand how the page is organized?
- Category focus: Headings, navigation, and readable section hierarchy
- Category note: This area is already easy for agents to work through.
- Passed: 4
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - LLMS TXT is structured: ✓ Has H1 title; ✓ Has blockquote description; ✓ Has 18 H2 sections; ✓ Has list items with links
- PASS - Links include descriptions: 413/413 links have descriptions
- PASS - Docs sections are structured: Found 7 recognized section types in H2 headings. Your sections: "instructions for llm agents", "constraints and requirements", "examples", "getting started", "build with nylas", "nylas for ai agents", "authentication", "email api", "calendar api", "scheduler", "notetaker", "notifications and webhooks", "cookbook", "api references", "sdks", "best practices", "platform", "optional"
- PASS - Optional sections are separated: Has an ## Optional section - AI tools can skip this content when context window is limited

### Task readiness - 100/100

- Question: Can an agent follow the instructions without guessing?
- Category focus: Examples, prerequisites, and action-ready instructions
- Category note: This area is already easy for agents to work through.
- Passed: 5
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - Product description is clear: Blockquote description has 44 words
- PASS - Constraints are documented: Found constraint indicators: note, authentication
- PASS - Integrations are documented: Found integration references: integration, plugin, connect
- PASS - Error handling is documented: Found error/troubleshooting references: error, troubleshoot, debug
- PASS - Examples are included: Found code blocks in content

### Access and recovery - 100/100

- Question: Can an agent complete the task without getting blocked?
- Category focus: Public access, cleaner output, and fewer dead ends
- Category note: This area is already easy for agents to work through.
- Passed: 5
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - Markdown routes resolve: 5/5 markdown pages return valid markdown content
- PASS - Pages respond quickly: Average response time: 156ms across 7 requests
- PASS - Content is readable without JS: Content is present in the initial HTML response (server-rendered)
- PASS - Markdown negotiation works: 3/3 pages return markdown when requested with Accept: text/markdown. Checked: ✓ https://developer.nylas.com/docs/v3/getting-started/, ✓ https://developer.nylas.com/docs/v3/getting-started/dashboard/, ✓ https://developer.nylas.com/docs/v3/getting-started/cli/
- PASS - Markdown output stays clean: Markdown content is clean (no navigation, footer, or cookie elements)


## Suggested Handoff

Ask the developer or coding agent to work through the failed checks and next-step items first, then rerun the benchmark on https://developer.nylas.com/ to confirm the score moves in the right direction.