--- title: "Waymark report for linktr.ee" canonical: "https://waymark.genedai.me/score/linktr.ee" last-updated: "2026-08-26T16:26:41.515Z" --- # Waymark report for linktr.ee Waymark scored linktr.ee 77/100 (B) on 26 Aug 2026. Score: 77/100 — Usable with gaps Scanned: 2026-08-26T16:26:41.515Z Canonical report: https://waymark.genedai.me/score/linktr.ee ## Layer breakdown - Discovery: 15.7/20 (13 of 20 eligible checks passed) - Access: 24.5/30 (32 of 43 eligible checks passed) - Usability: 29.1/40 (23 of 31 eligible checks passed) - Payments: N/A (excluded from the denominator) ## Findings ### 1. XML sitemap - Layer: discovery - Result: partial - Evidence: Sitemap referenced in robots.txt only. - Recommended fix: Add /sitemap.xml and reference it from robots.txt. ### 2. AGENTS.md - Layer: discovery - Result: failed - Evidence: agents.md status 404. - Recommended fix: Publish /agents.md with agent-oriented usage notes. ### 3. 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. ### 4. 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. ### 5. RSS or Atom feed - Layer: access - Result: failed - Evidence: No RSS/Atom link. - Recommended fix: Expose an RSS or Atom feed for machine subscribers. ### 6. 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. ### 7. 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. ### 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. Sitemap for agents - Layer: discovery - Result: partial - Evidence: Sitemap only referenced. - Recommended fix: Publish /sitemap.xml. ### 10. llms-full.txt - Layer: discovery - Result: failed - Evidence: llms-full.txt status 404. - Recommended fix: Optionally publish /llms-full.txt for one-shot ingest. ### 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. 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. 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. ### 17. 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. ### 18. robots.txt agent-user policy - Layer: access - Result: failed - Evidence: robots.txt Disallow: / covers agent-user crawlers (*). - Recommended fix: Stop blocking user-triggered agents in robots.txt. Remove any Disallow: / that applies to ChatGPT-User, Claude-User or Perplexity-User. Silence passes. ### 19. 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). ### 20. llms.txt links resolve - Layer: access - Result: partial - Evidence: 3 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. ### 21. 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. ### 22. Registry branding - Layer: discovery - Result: failed - Evidence: MCP card missing description, icon. - Recommended fix: Give your MCP server-card a display name, an icon or logo, and a description. ### 23. REST typed error model - Layer: usability - Result: failed - Evidence: OpenAPI 4xx/5xx responses lack a typed error schema. - Recommended fix: Document 4xx and 5xx responses with a typed error schema (or RFC 9457 problem+json). ### 24. REST response schema coverage - Layer: usability - Result: failed - Evidence: Few operations declare typed success response schemas. - Recommended fix: Define typed JSON response schemas for endpoints in your OpenAPI spec. ### 25. Function calling compatibility - Layer: usability - Result: failed - Evidence: Spec is missing unique operationIds/descriptions for function calling. - Recommended fix: Give endpoints unique operationIds, typed schemas, and descriptions for function calling. ### 26. 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.