AgentsReady
Verified deep dive · Devtools

Netlify

Run the agent liveReport a change
1 minTime to key
YesNo-human path
0Gates to a test key
9/10Onboarding score
Live keys only:CAPTCHAEmail verification

Fastest path to a key

  1. npm i -g netlify-cli
  2. zero-account option: `netlify deploy --allow-anonymous` gives a live URL with no account; human claims within 1 hour (`netlify claim` / claim link)
  3. for a credential: `netlify login --request "<agent> wants to login"` prints a login URL for the human plus a URL the agent polls; human signs up or signs in (GitHub/GitLab/Bitbucket/email)
  4. Email verification
    if signup was by email: verify email
  5. CLI token is usable as NETLIFY_AUTH_TOKEN. Long-lived PAT: User settings > Applications > Personal access tokens
  6. MCP: `npx -y add-mcp https://netlify-mcp.netlify.app/mcp` then OAuth in browser
  7. Working API key

Biggest gap

Anonymous mode covers deploys only (claim window just 1 hour); no scoped or fine-grained tokens and no API to mint them

Worth copying

`netlify login --request`: the agent gets a URL to hand the human and a URL to poll, so login works even when the agent is not on the user's machine

Sources (7) · checked 2026-10-11
92Readiness score / 100
L4 Agent-nativeBeats 98% of 1,846 companies
Access20/20
Context17/20
Interfaces32/32
Onboarding19/19
Trust4/9
llms.txt · root
MCP · https://mcp.netlify.com/mcp
OpenAPI · https://www.netlify.com/openapi.json

Biggest gains

  1. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
  2. +3 Public status page. Link a status page so agents can tell outages from bugs.
  3. +2 security.txt. Publish /.well-known/security.txt with a contact.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • FAILsecurity.txt2
  • FAILPublic status page3

Your fix pack: 4 changes, up to +8 points

Each change is ready to paste, filled in for netlify.com, with a command to check it worked. Or hand the whole list to your coding agent.

One file with your whole docs lets an agent load everything in a single request instead of crawling.

Where: https://netlify.com/llms-full.txt, regenerated on every docs deploy
# Mintlify, Fern, GitBook and ReadMe generate this automatically; turn it on in settings.
# Self-hosted docs: concatenate the markdown sources at build time
{ echo "# Netlify documentation"; for f in $(find docs -name "*.md*" | sort); do echo; echo "---"; echo "source: $f"; echo; cat "$f"; done; } > public/llms-full.txt
Check it worked:curl -s https://netlify.com/llms-full.txt | wc -c # expect well over 2000

Add the badge to your README

AgentsReady badge for netlify.com
[![AgentsReady](https://agentsready.dev/badge/netlify.com)](https://agentsready.dev/c/netlify.com)