---
title: "Waymark report for sendblue.com"
canonical: "https://waymark.genedai.me/score/sendblue.com"
last-updated: "2026-08-26T16:29:19.836Z"
---

# Waymark report for sendblue.com

Waymark scored sendblue.com 69.2/100 (C) on 26 Aug 2026.
Score: 69.2/100 — Blockers remain
Scanned: 2026-08-26T16:29:19.836Z
Canonical report: https://waymark.genedai.me/score/sendblue.com

## Layer breakdown

- Discovery: 14.6/20 (11 of 18 eligible checks passed)
- Access: 22.5/30 (24 of 34 eligible checks passed)
- Usability: 25.2/40 (7 of 13 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. RSS or Atom feed

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

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

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

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

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

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

- Layer: access
- Result: failed
- Evidence: Metadata lacks S256 PKCE.
- Recommended fix: Advertise S256 in code_challenge_methods_supported.

### 12. security.txt

- Layer: access
- Result: failed
- Evidence: No /.well-known/security.txt Contact.
- Recommended fix: Publish /.well-known/security.txt with a Contact field.

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

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

### 15. Idempotency signal

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

### 16. OpenAPI document

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

### 17. MCP server

- Layer: usability
- Result: partial
- Evidence: MCP mentioned without a documented initialize.
- Recommended fix: Publish an MCP card or document the MCP URL in llms.txt, then answer initialize.

### 18. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching sendblue.com.
- 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: 1 real, 1 homepage-shell, 4 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. auth.md structure

- Layer: usability
- Result: failed
- Evidence: auth.md exists but is missing the WorkOS-style sections (1 hits).
- Recommended fix: Structure /auth.md with Discover, Register, Claim, Use, Errors, and Revocation (WorkOS auth.md).

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