---
title: "Waymark report for vercel.com"
canonical: "https://waymark.genedai.me/score/vercel.com"
last-updated: "2026-09-07T11:59:15.246Z"
---

# Waymark report for vercel.com

Waymark scored vercel.com 88.9/100 (A) on 7 Sep 2026.
Score: 88.9/100 — Mostly ready
Scanned: 2026-09-07T11:59:15.246Z
Canonical report: https://waymark.genedai.me/score/vercel.com

## Layer breakdown

- Discovery: 18.6/20 (18 of 20 eligible checks passed)
- Access: 28.5/30 (37 of 41 eligible checks passed)
- Usability: 32.9/40 (23 of 28 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. RSS or Atom feed

- Layer: access
- Result: failed
- Evidence: No RSS/Atom link.
- Recommended fix: Expose an RSS or Atom feed for machine subscribers.

### 2. CORS / API hint

- Layer: access
- Result: partial
- Evidence: No CORS header or obvious API path.
- Recommended fix: If you expose an API, send Access-Control-Allow-Origin for intended clients.

### 3. MCP well-known card

- Layer: usability
- Result: failed
- Evidence: MCP mentioned without a well-known card.
- Recommended fix: Publish /.well-known/mcp.json describing your MCP server.

### 4. robots.txt AI policy

- Layer: discovery
- Result: partial
- Evidence: robots.txt present but no named AI crawlers.
- Recommended fix: Name GPTBot, ClaudeBot, Google-Extended, PerplexityBot and state allow or deny.

### 5. MCP server card

- Layer: usability
- Result: partial
- Evidence: MCP mentioned without a card.
- Recommended fix: Publish /.well-known/mcp.json or mcp/server-card.json.

### 6. ai-plugin.json

- Layer: discovery
- Result: failed
- Evidence: No /.well-known/ai-plugin.json.
- Recommended fix: Optionally publish a plugin-style capability manifest.

### 7. change-password well-known

- Layer: access
- Result: failed
- Evidence: Login surface without /.well-known/change-password.
- Recommended fix: If users have passwords, serve /.well-known/change-password.

### 8. Rate limit signal

- Layer: usability
- Result: partial
- Evidence: API surface without a rate-limit signal.
- Recommended fix: Document or send rate-limit headers on APIs.

### 9. Idempotency signal

- Layer: usability
- Result: partial
- Evidence: API surface without idempotency notes.
- Recommended fix: Document idempotency keys for mutating calls.

### 10. Markdown frontmatter metadata

- Layer: access
- Result: failed
- Evidence: Served markdown has no YAML frontmatter block.
- Recommended fix: Open served markdown with a --- frontmatter block carrying title plus description, canonical, or last-updated.

### 11. Multi-language SDK packages

- Layer: usability
- Result: partial
- Evidence: npm matches; second ecosystem homepage does not.
- Recommended fix: Publish official SDK packages on npm and PyPI whose homepage is this domain.

## Interpretation

Public technical snapshot; not a guarantee of task completion. Private and authenticated workflows are outside this scan. Cite scanned_at and the canonical report URL; the URL serves the latest completed snapshot and can change after a rescan.

The official Waymark score is Discovery 20 / Access 30 / Usability 40 / Payments 10. N/A and scanner-error checks drop out of the denominator; they are not scored as failures. An observed agent journey is supporting evidence and does not change the numeric score.