---
title: "Waymark report for genedai.me"
canonical: "https://waymark.genedai.me/score/genedai.me"
last-updated: "2026-08-23T13:59:56.776Z"
---

# Waymark report for genedai.me

Waymark scored genedai.me 43.5/100 (D) on 23 Aug 2026.
Score: 43.5/100 — Major gaps
Scanned: 2026-08-23T13:59:56.776Z
Canonical report: https://waymark.genedai.me/score/genedai.me

## Layer breakdown

- Discovery: 17.5/30 (7 of 12 eligible checks passed)
- Access: 10.4/25 (2 of 6 eligible checks passed)
- Usability: 0/20 (0 of 5 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. 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.

### 5. OAuth / OIDC well-known

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

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

### 7. MCP well-known card

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

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

### 9. openapi.json fetchable

- Layer: usability
- Result: failed
- Evidence: No fetchable OpenAPI document.
- Recommended fix: Host a machine-readable OpenAPI document at /openapi.json.

### 10. Webhook or API docs

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

### 11. Agent skills index

- Layer: usability
- Result: failed
- Evidence: No agent-skills index.
- Recommended fix: Publish /.well-known/agent-skills/index.json or SKILL.md.

### 12. llms-full.txt

- Layer: discovery
- Result: failed
- Evidence: llms-full.txt status 404.
- Recommended fix: Optionally publish /llms-full.txt for one-shot ingest.

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

### 14. Markdown negotiation

- Layer: access
- Result: failed
- Evidence: Homepage did not negotiate markdown.
- Recommended fix: Respond to Accept: text/markdown with a markdown body.

### 15. /index.md fallback

- Layer: access
- Result: failed
- Evidence: index.md status 404.
- Recommended fix: Serve a markdown homepage at /index.md.

### 16. ai-plugin.json

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

### 17. Web Bot Auth keys

- Layer: access
- Result: failed
- Evidence: No http-message-signatures-directory.
- Recommended fix: Publish a public-key directory for signed agent requests.

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