---
title: "Waymark report for upstash.com"
canonical: "https://waymark.genedai.me/score/upstash.com"
last-updated: "2026-08-26T16:30:28.862Z"
---

# Waymark report for upstash.com

Waymark scored upstash.com 70.4/100 (B) on 26 Aug 2026.
Score: 70.4/100 — Usable with gaps
Scanned: 2026-08-26T16:30:28.862Z
Canonical report: https://waymark.genedai.me/score/upstash.com

## Layer breakdown

- Discovery: 16.4/20 (14 of 19 eligible checks passed)
- Access: 23.8/30 (27 of 36 eligible checks passed)
- Usability: 23.1/40 (8 of 15 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. RSS or Atom feed

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

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

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

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

### 9. NLWeb /ask

- Layer: usability
- Result: partial
- Evidence: NLWeb or /ask signal.
- Recommended fix: Offer a structured /ask endpoint if you do NL retrieval.

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

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

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

### 13. Web app manifest

- Layer: access
- Result: partial
- Evidence: manifest link without a fetchable file.
- Recommended fix: Host /manifest.webmanifest if the site is installable.

### 14. Idempotency signal

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

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

### 16. OpenAPI document

- Layer: access
- Result: failed
- 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. Sitemap lastmod

- Layer: discovery
- Result: failed
- Evidence: Sitemap without lastmod.
- Recommended fix: Add lastmod dates to sitemap entries.

### 19. llms.txt links resolve

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

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

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