---
title: "Waymark report for digidai.github.io"
canonical: "https://waymark.genedai.me/score/digidai.github.io"
last-updated: "2026-09-13T11:43:40.273Z"
---

# Waymark report for digidai.github.io

Waymark scored digidai.github.io 52.4/100 (C) on 13 Sep 2026.
Score: 52.4/100 — Blockers remain
Scanned: 2026-09-13T11:43:40.273Z
Canonical report: https://waymark.genedai.me/score/digidai.github.io

## Layer breakdown

- Discovery: 15.2/20 (11 of 17 eligible checks passed)
- Access: 19.5/30 (24 of 36 eligible checks passed)
- Usability: 12.5/40 (3 of 8 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. CSP or X-Frame-Options

- Layer: access
- Result: failed
- Evidence: Neither CSP nor X-Frame-Options on homepage.
- Recommended fix: Send Content-Security-Policy or X-Frame-Options.

### 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. Webhook or API docs

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

### 7. llms-full.txt

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

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

### 9. Markdown negotiation

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

### 10. ai-plugin.json

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

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

### 12. Idempotency signal

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

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

### 14. OpenAPI document

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

### 15. Developer portal

- Layer: access
- Result: partial
- Evidence: No developer portal.
- Recommended fix: Offer a self-serve docs hub.

### 16. Pricing page

- Layer: access
- Result: failed
- Evidence: No pricing page.
- Recommended fix: Publish /pricing.

### 17. CLI tool

- Layer: usability
- Result: failed
- Evidence: No CLI mention.
- Recommended fix: Publish an official CLI.

### 18. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching digidai.github.io.
- Recommended fix: Publish an official package whose homepage is this domain.

### 19. Agent instruction / when-to-use

- Layer: access
- Result: failed
- Evidence: Agent file exists without when-to-use guidance.
- Recommended fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases.

### 20. Organization schema completeness

- Layer: access
- Result: failed
- Evidence: Organization JSON-LD missing contactPoint and address.
- Recommended fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress).

### 21. llms.txt links resolve

- Layer: access
- Result: partial
- Evidence: 7 real, 1 homepage-shell, 0 dead of 8 sampled links.
- Recommended fix: Make every link your llms.txt declares resolve to real content, not a homepage shell 200.

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

### 23. Agent-UA markdown docs

- Layer: access
- Result: failed
- Evidence: Docs host did not serve markdown to GPTBot (HTTP 526, text/plain; charset=utf-8).
- Recommended fix: Serve text/markdown to GPTBot (and similar agent UAs) on your docs host.

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