genedai.me
Journey
43.5/ 100
D · Not ready for agents
Waymark scored genedai.me 43.5/100 (D) on 23 Aug 2026.
genedai.me is major gaps. meaning is the strongest layer, and Usability is the open one. Next: aGENTS.md.
FindMixed
17.5/30
7 of 12 checks passed
MeaningMixed
15.6/25
5 of 8 checks passed
DoorWeak
10.4/25
2 of 6 checks passed
ToolsWeak
0/20
0 of 5 checks passed
Group by
1. Can an agent discover and trust you? 56/100
Whether an agent can find this origin from public files and treat it as the real one.
pass
HTTPS reachable
1/1
Evidence. Homepage responded 200 over HTTPS.
Probed homepage.
pass
robots.txt present
1/1
Evidence. Valid robots.txt with User-agent rules.
Probed robots.txt.
pass
XML sitemap
1/1
Evidence. Found sitemap.xml or sitemap index.
failed
Well-known AI catalog
0/1
Evidence. No ai-plugin.json or ai-catalog.json.
Recommended fix. Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json.
failed
AGENTS.md
0/1
Evidence. agents.md status 404.
Probed public URLs named in the evidence.
Recommended fix. Publish /agents.md with agent-oriented usage notes.
pass
robots.txt AI policy
Required
1/1
Evidence. Named AI crawlers: GPTBot, ChatGPT-User, CCBot, anthropic-ai, Claude-Web, PerplexityBot.
pass
Sitemap for agents
Recommended
1/1
Evidence. Sitemap document fetched.
Probed sitemap.
failed
HTTP Link header
bonus
0/1
Evidence. No rel=sitemap|describedby|api-catalog|alternate on homepage.
Probed homepage + sitemap.
Recommended fix. Send RFC 8288 Link headers for related machine resources.
failed
ai-plugin.json
bonus
0/1
Evidence. No /.well-known/ai-plugin.json.
Probed well-known paths.
Recommended fix. Optionally publish a plugin-style capability manifest.
n/a
API catalog linkset
bonus
0/1
Evidence. No public API catalog (N/A).
2. Do you welcome agents? 63/100
Whether crawlers and signed bots are allowed through rather than blocked at the door.
pass
AI crawlers not blanket-blocked
1/1
Evidence. No blanket Disallow: / for common AI bots.
failed
Web Bot Auth keys
Recommended
0/1
Evidence. No http-message-signatures-directory.
Recommended fix. Publish a public-key directory for signed agent requests.
partial
CORS / API hint
0.5/1
Evidence. No CORS header or obvious API path.
Recommended fix. If you expose an API, send Access-Control-Allow-Origin for intended clients.
pass
CSP or X-Frame-Options
1/1
Evidence. CSP or X-Frame-Options present.
3. Does an agent understand who you are and what you do? 88/100
Whether the site explains the product in language a model can ingest.
pass
Title and description
1/1
Evidence. Title and meta description present.
pass
JSON-LD structured data
1/1
Evidence. application/ld+json script found.
pass
html lang attribute
1/1
Evidence. html[lang] is set.
pass
JSON-LD entities
Recommended
1/1
Evidence. Recognized schema.org types in JSON-LD.
pass
llms.txt
1/1
Evidence. Found /llms.txt with content.
pass
llms.txt index
Recommended
1/1
Evidence. llms.txt has content.
failed
llms-full.txt
bonus
0/1
Evidence. llms-full.txt status 404.
Probed public URLs named in the evidence.
Recommended fix. Optionally publish /llms-full.txt for one-shot ingest.
n/a
NLWeb schemamap
bonus
0/1
Evidence. No schemamap (N/A unless you offer NL search).
n/a
Speakable markup
bonus
0/1
Evidence. No SpeakableSpecification (N/A unless voice content).
pass
RSS or Atom feed
1/1
Evidence. Feed link detected.
4. Can an agent integrate with you? 0/100
Whether there is a documented machine door into the product.
failed
OpenAPI / Swagger link
0/1
Evidence. No OpenAPI/Swagger link in HTML.
Probed OpenAPI.
Recommended fix. Link to an OpenAPI or Swagger document from the homepage.
failed
Login or docs link
0/1
Evidence. No login/docs/developers link.
Recommended fix. Link to login and developer documentation from the homepage.
failed
MCP well-known card
0/1
Evidence. No /.well-known/mcp.json card.
Probed well-known paths.
Recommended fix. Publish /.well-known/mcp.json describing your MCP server.
failed
MCP SSE / HTTP hint
0/1
Evidence. No MCP/SSE hint on the homepage.
Probed homepage.
Recommended fix. Document an MCP HTTP or SSE endpoint.
failed
openapi.json fetchable
0/1
Evidence. No fetchable OpenAPI document.
Probed OpenAPI.
Recommended fix. Host a machine-readable OpenAPI document at /openapi.json. Verify: curl -sI https://genedai.me/openapi.json
failed
Webhook or API docs
0/1
Evidence. No webhook/API docs mention.
Recommended fix. Document webhooks and REST/RPC APIs for agents.
failed
Agent skills index
0/1
Evidence. No agent-skills index.
Recommended fix. Publish /.well-known/agent-skills/index.json or SKILL.md.
n/a
OpenAPI document
Required
0/1
Evidence. No HTTP API surface detected (N/A).
n/a
MCP server card
Recommended
0/1
Evidence. No MCP surface (N/A).
n/a
Agent Skills files
bonus
0/1
Evidence. No SKILL.md surface (N/A).
5. Is your integration well-built? N/A
Whether the integration surface is complete enough to call with confidence.
n/a
MCP initialize
Required
0/1
Evidence. No MCP card to initialize
n/a
MCP server card
Recommended
0/1
Evidence. No MCP surface (N/A).
6. Can an agent use you reliably in production? N/A
Whether errors, idempotency, and limits are visible before a call fails.
7. Can an agent authenticate to you? 0/100
Whether an agent can obtain access without a human in the loop.
failed
OAuth / OIDC well-known
0/1
Evidence. No oauth-authorization-server or openid-configuration.
Recommended fix. Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents.
n/a
OAuth 2.0 surface
Required
0/1
Evidence. No delegated-access surface (N/A).
n/a
OAuth AS metadata
Required
0/1
Evidence. No AS metadata (N/A unless you run an AS).
n/a
PKCE S256
Required
0/1
Evidence. No OAuth metadata to evaluate PKCE.
n/a
OAuth protected resource
Recommended
0/1
Evidence. No OAuth resource metadata (N/A).
8. Can an agent transact with you? N/A
Whether an agent can price, pay, or check out on a documented rail.
n/a
x402 payment
bonus
0/1
Evidence. No x402 (N/A unless you charge per call).
n/a
Agentic checkout (ACP)
bonus
0/1
Evidence. No ACP (N/A unless agent checkout).
n/a
ACP delegated payment
bonus
0/1
Evidence. No delegated payment (N/A).
n/a
Universal Commerce Protocol
bonus
0/1
Evidence. No /.well-known/ucp (N/A).
Probed well-known paths.
n/a
Machine Payments Protocol
bonus
0/1
Evidence. No MPP (N/A).
9. Can a user act through an agent? N/A
Whether a person can finish a job through an agent-facing UI.
n/a
MCP Apps UI hint
bonus
0/1
Evidence. No MCP Apps hint (N/A unless you return UI).
n/a
A2A agent card
Required
0/1
Evidence. No agent-card.json (N/A unless A2A).
10. Can an agent operate your website directly? 0/100
Whether an agent can read and operate the site itself when there is no API or MCP.
failed
Markdown negotiation
bonus
0/1
Evidence. Homepage did not negotiate markdown.
Probed homepage.
Recommended fix. Respond to Accept: text/markdown with a markdown body.
failed
/index.md fallback
bonus
0/1
Evidence. index.md status 404.
Probed public URLs named in the evidence.
Recommended fix. Serve a markdown homepage at /index.md.
n/a
WebMCP page tools
bonus
0/1
Evidence. No in-page WebMCP (N/A).
n/a
NLWeb /ask
bonus
0/1
Evidence. No NLWeb /ask (N/A).
About this snapshot & how to cite it
Public technical signals observed by Waymark. A score describes this snapshot; it does not guarantee that an agent will complete a task. Private and authenticated workflows are outside this scan.
Snapshot: . Cite the domain, score, scan time, and report URL. This URL serves the latest completed snapshot and can change after a rescan.
Share this snapshot
Also on the Board
- ora.ai90.9/100 · AScan them →
- superset.sh90.7/100 · AScan them →
- waymark.genedai.me87.2/100 · AScan them →
Email me if this score changes
Join the monitoring waitlist. Monitoring is not active yet. This saves your interest; it does not schedule scans or send change alerts.
Email this report
Send the current snapshot and a link. One email. Not a list.