---
title: "Waymark report for firecrawl.dev"
canonical: "https://waymark.genedai.me/score/firecrawl.dev"
last-updated: "2026-08-24T00:54:30.449Z"
---

# Waymark report for firecrawl.dev

Waymark scored firecrawl.dev 77.8/100 (B) on 24 Aug 2026.
Score: 77.8/100 — Usable with gaps
Scanned: 2026-08-24T00:54:30.449Z
Canonical report: https://waymark.genedai.me/score/firecrawl.dev

## Layer breakdown

- Discovery: 16.8/20 (13 of 17 eligible checks passed)
- Access: 20.8/30 (18 of 27 eligible checks passed)
- Usability: 32.4/40 (11 of 15 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

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

### 2. JSON-LD structured data

- Layer: access
- Result: failed
- Evidence: No JSON-LD on the homepage.
- Recommended fix: Add JSON-LD (Organization, WebSite, or SoftwareApplication).

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

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

### 8. JSON-LD entities

- Layer: access
- Result: failed
- Evidence: No JSON-LD.
- Recommended fix: Embed Organization, Product, Offer, SoftwareApplication, or FAQPage.

### 9. Markdown negotiation

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

### 10. MCP Apps UI hint

- Layer: usability
- Result: failed
- Evidence: No MCP Apps hint (N/A unless you return UI).
- Recommended fix: If you return UI, declare io.modelcontextprotocol/ui resources.

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

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

- Layer: access
- Result: failed
- Evidence: No about/privacy/contact link.
- Recommended fix: Link about or privacy from the homepage.

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