---
title: "Waymark report for galileo.ai"
canonical: "https://waymark.genedai.me/score/galileo.ai"
last-updated: "2026-08-26T16:22:42.805Z"
---

# Waymark report for galileo.ai

Waymark scored galileo.ai 76.1/100 (B) on 26 Aug 2026.
Score: 76.1/100 — Usable with gaps
Scanned: 2026-08-26T16:22:42.805Z
Canonical report: https://waymark.genedai.me/score/galileo.ai

## Layer breakdown

- Discovery: 14.6/20 (11 of 19 eligible checks passed)
- Access: 19.1/30 (20 of 31 eligible checks passed)
- Usability: 34.8/40 (14 of 17 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. 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. CSP or X-Frame-Options

- Layer: access
- Result: failed
- Evidence: Neither CSP nor X-Frame-Options on homepage.
- Recommended fix: Send Content-Security-Policy or X-Frame-Options.

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

### 7. Webhook or API docs

- Layer: usability
- Result: failed
- Evidence: No webhook/API docs mention.
- Recommended fix: Document webhooks and REST/RPC APIs for agents.

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

### 9. llms-full.txt

- Layer: discovery
- Result: failed
- Evidence: llms-full.txt status 404.
- Recommended fix: Optionally publish /llms-full.txt for one-shot ingest.

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

### 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. Public API surface

- Layer: access
- Result: failed
- Evidence: No public API or docs surface.
- Recommended fix: Document a public API at /docs or /developers.

### 15. Sitemap lastmod

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

### 16. Content without JavaScript

- Layer: access
- Result: failed
- Evidence: Raw HTML is thin for agents (H1=false, 163 chars).
- Recommended fix: Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

### 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. Schema type breadth

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

### 19. llms.txt links resolve

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

### 20. Accessible document structure

- Layer: usability
- Result: failed
- Evidence: Homepage HTML lacks main/nav/H1 document structure.
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

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

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