Agent readiness · Application hosting and deployment
vercel.com
Measured under an older formula
This scan ran under formula 9.2 and we are on 9.31 now, so the number below is not comparable with the corpus and the sentences may quote addresses we have since moved. We keep the page rather than delete it, and keep it out of search rather than publish it. Rescan it and this page catches up.
11 of 15 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. 1 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)
- PASSllms.txt publishedllms.txt present at https://vercel.com/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript9,138 characters of text without JS, on https://vercel.com/docs/sign-in-with-vercel/tokens rather than on https://vercel.com/docs
- 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
- PASSOAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
- PASSMCP surfaceLive MCP endpoint at https://mcp.vercel.com/v1/mcp, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://vercel.com/signup 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.
- FAILSignup reachable without a browserhttps://vercel.com/signup is reachable, but its form needs JavaScript
D · Provisioning
- PARTProgrammatic key provisioning1 of 7 provisioning phrases across the 5 documents we read: "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://vercel.com/pricing: "free trial", "$0"
E · Integration
- PASSTyped SDK on the registry@vercel/sdk@1.28.17 ships types
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://vercel.com/docs
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 vercel.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.