---
title: "Waymark report for clerk.com"
canonical: "https://waymark.genedai.me/score/clerk.com"
last-updated: "2026-08-24T02:15:05.862Z"
---

# Waymark report for clerk.com

Waymark scored clerk.com 74.4/100 (B) on 24 Aug 2026.
Score: 74.4/100 — Usable with gaps
Scanned: 2026-08-24T02:15:05.862Z
Canonical report: https://waymark.genedai.me/score/clerk.com

## Layer breakdown

- Discovery: 17.1/20 (15 of 19 eligible checks passed)
- Access: 20.6/30 (16 of 24 eligible checks passed)
- Usability: 29.2/40 (9 of 15 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. AGENTS.md

- Layer: discovery
- Result: failed
- Evidence: agents.md status 404.
- Recommended fix: Publish /agents.md with agent-oriented usage notes.

### 2. Well-known AI catalog

- Layer: discovery
- Result: failed
- Evidence: No ai-plugin.json or ai-catalog.json.
- Recommended fix: Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json.

### 3. OpenAPI / Swagger link

- Layer: access
- Result: failed
- Evidence: No OpenAPI/Swagger link in HTML.
- Recommended fix: Link to an OpenAPI or Swagger document from the homepage.

### 4. OAuth / OIDC well-known

- Layer: access
- Result: partial
- Evidence: No oauth-authorization-server or openid-configuration.
- Recommended fix: Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents.

### 5. Login or docs link

- Layer: access
- Result: failed
- Evidence: No login/docs/developers link.
- Recommended fix: Link to login and developer documentation from the homepage.

### 6. AI crawlers not blanket-blocked

- Layer: access
- Result: failed
- Evidence: robots.txt Disallow: / for * or common AI bots.
- Recommended fix: Avoid Disallow: / for GPTBot, ClaudeBot, PerplexityBot unless intentional.

### 7. MCP SSE / HTTP hint

- Layer: usability
- Result: failed
- Evidence: No MCP/SSE hint on the homepage.
- Recommended fix: Document an MCP HTTP or SSE endpoint.

### 8. Webhook or API docs

- Layer: usability
- Result: failed
- Evidence: No webhook/API docs mention.
- Recommended fix: Document webhooks and REST/RPC APIs for agents.

### 9. HTTP Link header

- Layer: discovery
- Result: failed
- Evidence: No rel=sitemap|describedby|api-catalog|alternate on homepage.
- Recommended fix: Send RFC 8288 Link headers for related machine resources.

### 10. MCP Apps UI hint

- Layer: usability
- Result: failed
- Evidence: No MCP Apps hint (N/A unless you return UI).
- Recommended fix: If you return UI, declare io.modelcontextprotocol/ui resources.

### 11. ai-plugin.json

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

### 12. 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.

### 13. 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.

### 14. Idempotency signal

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

### 15. Machine-readable errors

- Layer: usability
- Result: partial
- Evidence: API surface without a JSON error shape.
- Recommended fix: Return a JSON or problem+json error body.

### 16. OpenAPI document

- Layer: access
- Result: failed
- Evidence: OpenAPI probe.
- Recommended fix: Publish an OpenAPI document at a stable URL.

### 17. Trust pages

- Layer: access
- Result: failed
- Evidence: No about/privacy/contact link.
- Recommended fix: Link about or privacy from the homepage.

### 18. RSS or Atom document

- Layer: access
- Result: partial
- Evidence: No /feed or /rss.xml document.
- Recommended fix: Publish /rss.xml or /atom.xml.

## 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.