---
title: "Waymark report for render.com"
canonical: "https://waymark.genedai.me/score/render.com"
last-updated: "2026-08-24T02:18:59.418Z"
---

# Waymark report for render.com

Waymark scored render.com 81.2/100 (B) on 24 Aug 2026.
Score: 81.2/100 — Usable with gaps
Scanned: 2026-08-24T02:18:59.418Z
Canonical report: https://waymark.genedai.me/score/render.com

## Layer breakdown

- Discovery: 16.3/20 (13 of 18 eligible checks passed)
- Access: 24.5/30 (19 of 24 eligible checks passed)
- Usability: 32.2/40 (11 of 15 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. 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. 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. 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. Sitemap for agents

- Layer: discovery
- Result: partial
- Evidence: Sitemap only referenced.
- Recommended fix: Publish /sitemap.xml.

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

### 8. ai-plugin.json

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

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

### 13. Scoped permissions

- Layer: access
- Result: failed
- Evidence: No named OAuth scopes.
- Recommended fix: Declare OAuth scopes in a spec.

### 14. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching render.com.
- Recommended fix: Publish an official package 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.