---
title: "Waymark report for turso.tech"
canonical: "https://waymark.genedai.me/score/turso.tech"
last-updated: "2026-08-26T16:30:30.846Z"
---

# Waymark report for turso.tech

Waymark scored turso.tech 82.3/100 (B) on 26 Aug 2026.
Score: 82.3/100 — Usable with gaps
Scanned: 2026-08-26T16:30:30.846Z
Canonical report: https://waymark.genedai.me/score/turso.tech

## Layer breakdown

- Discovery: 14.3/20 (12 of 20 eligible checks passed)
- Access: 26.1/30 (33 of 41 eligible checks passed)
- Usability: 33.7/40 (17 of 21 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. 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.

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

### 7. ai-plugin.json

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

### 8. API catalog linkset

- Layer: discovery
- Result: failed
- Evidence: API present without RFC 9727 catalog.
- Recommended fix: Add /.well-known/api-catalog pointing at OpenAPI.

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

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

### 11. Idempotency signal

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

### 12. RSS or Atom document

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

### 13. Package homepage match

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

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

### 15. Schema type breadth

- Layer: access
- Result: failed
- Evidence: JSON-LD only has Organization, ContactPoint, PostalAddress.
- Recommended fix: Expand your JSON-LD beyond Organization/WebSite. Add FAQPage, Service or Product, AggregateRating or Review, and BreadcrumbList.

### 16. llms.txt links resolve

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

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

### 18. Accessible document structure

- Layer: usability
- Result: partial
- Evidence: Landmarks partial (main=false nav=true h1=true skip=false).
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

### 19. Registry branding

- Layer: discovery
- Result: failed
- Evidence: MCP card missing icon.
- Recommended fix: Give your MCP server-card a display name, an icon or logo, and a description.

### 20. Multi-language SDK packages

- Layer: usability
- Result: failed
- Evidence: No npm+PyPI official packages whose homepage is this domain.
- 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.