vercel.com
Strong technical baseline
Technical readiness score
The agent completed the observed task
One run shows how an agent performed, but it does not determine the technical score.
Task
What does vercel.com do and who is it for? Explain it back to me.
17 steps5 reasoning steps5 searches
Critical access needs attention
These checks describe whether an ordinary agent can enter, read, and operate the public site.
- 3 / 3 passed
Agents can reach the site
Crawler access, bot defenses, and explicit agent policy.
- 1 / 2 passed
Core content is available
Useful content remains accessible without a fragile browser-only path.
- 1 / 2 passed
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
- 4 / 4 passed
Controls are understandable
Forms and interactive controls expose usable names and structure.
Advertised capabilities need refinement
Optional surfaces appear only when the scan finds positive evidence that the site offers them.
Public website
Ready with gaps
14 of 20 mature checks passed
API
Ready with gaps
10 of 16 mature checks passed
Authentication
Strong
3 of 3 mature checks passed
MCP
Ready with gaps
0 of 1 mature checks passed
Fix these gaps first
Critical access gaps come first, followed by gaps in capabilities the site advertises.
- 01Critical access
Agent-friendly 404s
Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with `curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist` - it must print 404.
- 02Critical access
Content without JavaScript
Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
- 03Advertised capabilities
Idempotency-Key support
Support an idempotency key on your write operations and declare it where agents can read it: an Idempotency-Key header parameter on your POST/PUT/PATCH operations in your OpenAPI spec for REST, or a client-supplied id argument on your GraphQL mutations. Agents retry on network failures, and without this a retry can double-charge or duplicate a record.
- 04Advertised capabilities
Content efficiency
Reduce markup overhead so readable text is at least 5% of your HTML. Strip unused inline scripts/styles, server-render content instead of shipping large JSON hydration blobs, and keep wrapper nesting shallow.
- 05Advertised capabilities
Rate limit response headers
Return standard rate-limit headers on your API responses (the RFC RateLimit headers, plus Retry-After on a 429) so agents can self-throttle in real time, and document the conventions alongside your API.
Audit the checks behind the score
Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.
Essential9 of 11 passed · 67.9 / 80 points
- Content without JavaScriptPartial (33%)
- Not blocked by bot detectionPassed
- robots.txt agent-user policyPassed
- Redirect hygienePassed
- Content behind authPassed
- OpenAPI spec publishedPassed
- Agent crawler reachabilityPassed
- OAuth 2.0 supportPassed
- Scoped permissionsPassed
- JSON error responsesPassed
- Agent-friendly 404sFailed
Recommended18 of 29 passed · 15.3 / 20 points
- Developer resource discoverabilityPassed
- Brand name discoverabilityPassed
- robots.txt AI crawler policyPassed
- Sitemap existsPassed
- Content efficiencyFailed
- Content crawl depth signalsFailed
- JSON-LD structured dataPassed
- Public API/docs linked from homepagePassed
- Agent instruction / when-to-usePartial (67%)
- Metadata completenessPassed
- Organization schema completenessPartial (50%)
- Trust anchor pagesPassed
- Page token budgetPassed
- Code fence validityPassed
- Developer portalPassed
- Public API with reachable endpointsPassed
- Agent onboarding frictionPassed
- MCP server / manifestPartial (83%)
- Rate limit response headersFailed
- Idempotency-Key supportFailed
- REST typed error modelPassed
- REST versioning / deprecation policyPassed
- REST pagination patternPassed
- REST async-job patternPartial (50%)
- CLI tool availablePassed
- Multi-language SDK packagesPartial (67%)
- REST response schema coveragePassed
- API schema complexity analysisPartial (50%)
- Function calling compatibilityPartial (50%)
Bonus signals32 positive · +5 points
- ARD / ai-catalogPassed
- ARD entry validityPassed
- Wikipedia / Wikidata entity presencePassed
- Listed in MCP registriesPassed
- NPM/PyPI SDK packagePassed
- Agent platform configsPassed
- ChatGPT app listedPassed
- Agent discovery filePassed
- pricing.md existsPartial (50%)
- MCP well-known discoveryPassed
- HTTP Link headers (RFC 8288)Passed
- Sitemap freshness (lastmod)Passed
- llms.txt existsPassed
- llms.txt formattingPartial (50%)
- llms.txt links resolvePassed
- API catalog (RFC 9727)Partial (50%)
- Markdown agent docsPassed
- Markdown content negotiation (acceptmarkdown.com)Passed
- MCP auth mechanismPassed
- MCP OAuth metadataPassed
- MCP PKCE S256 supportPassed
- OAuth Protected Resource metadata (RFC 9728)Passed
- Agent auth discovery metadataPartial (33%)
- Agent auth WWW-Authenticate hintPassed
- Product + docs MCP coveragePartial (50%)
- Sandbox / test environmentPassed
- REST batch / bulk endpointPassed
- Accessible document structurePassed
- Native interactive controlsPassed
- Accessible names on controlsPassed
- Form control labelingPassed
- Accessibility-tree injection safety (bonus)Passed
Inspect the underlying audit
The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.
Score alerts
A weekly report with ranking changes, new agent feedback, and score alerts for vercel.com.
Source: Ora API
Snapshot 2026-08-19T09-19-58-406Z