digidai.github.io
Journey
52.4/ 100
C · Needs work
Waymark scored digidai.github.io 52.4/100 (C) on 13 Sep 2026.
digidai.github.io is blockers remain. Discovery is the strongest layer, and Usability is the open one. Next: openAPI document.
FindMixed
15.2/20
11 of 17 checks passed
DoorMixed
19.5/30
24 of 36 checks passed
ToolsWeak
12.5/40
3 of 8 checks passed
Pay
N/A
No cart or pay rail — out of the denominator.
Group by
1. Can an agent discover and trust you? 71/100
Whether an agent can find this origin from public files and treat it as the real one.
pass
HTTPS reachable
2/2
Evidence. Homepage responded 200 over HTTPS.
Probed homepage.
pass
robots.txt present
2/2
Evidence. Valid robots.txt with User-agent rules.
Probed robots.txt.
pass
XML sitemap
2/2
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
2/2
Evidence. Named AI crawlers: ClaudeBot, GPTBot, ChatGPT-User, CCBot, anthropic-ai, Claude-Web.
pass
Sitemap for agents
Recommended
2/2
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/2
Evidence. No public API catalog (N/A).
scanner error
Wikipedia sitelink
bonus
0/4
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
scanner error
Wikidata official website
bonus
0/3
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
scanner error
Brand official-website match
Recommended
0/3
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
pass
Public MCP registry listing
bonus
1/1
Evidence. Registry hit at https://glama.ai/mcp/servers?query=digidai.
Probed public URLs named in the evidence.
failed
Package homepage match
bonus
0/1
Evidence. No npm package homepage matching digidai.github.io.
Probed homepage.
Recommended fix. Publish an official package whose homepage is this domain.
pass
Sitemap lastmod
bonus
1/1
Evidence. Sitemap has lastmod.
n/a
related-website-set
bonus
0/1
Evidence. No related-website-set (N/A unless multi-origin).
n/a
ads.txt
bonus
0/1
Evidence. No ads inventory (N/A).
2. Do you welcome agents? 83/100
Whether crawlers and signed bots are allowed through rather than blocked at the door.
pass
AI crawlers not blanket-blocked
2/2
Evidence. No blanket Disallow: / for common AI bots.
n/a
robots Crawl-delay
bonus
0/1
Evidence. No Crawl-delay (optional).
n/a
Web Bot Auth keys
Recommended
0/2
Evidence. No http-message-signatures-directory.
pass
CORS / API hint
1/1
Evidence. CORS header or API path hint found.
failed
CSP or X-Frame-Options
0/1
Evidence. Neither CSP nor X-Frame-Options on homepage.
Probed homepage.
Recommended fix. Send Content-Security-Policy or X-Frame-Options.
pass
robots.txt agent-user policy
Required
2/2
Evidence. No Disallow: / for ChatGPT-User, Claude-User, or Perplexity-User (silence passes).
3. Does an agent understand who you are and what you do? 84/100
Whether the site explains the product in language a model can ingest.
pass
Title and description
2/2
Evidence. Title and meta description present.
pass
JSON-LD structured data
4/4
Evidence. application/ld+json script found.
pass
html lang attribute
1/1
Evidence. html[lang] is set.
pass
JSON-LD entities
Recommended
4/4
Evidence. Recognized schema.org types in JSON-LD.
pass
JSON-LD sameAs
bonus
2/2
Evidence. sameAs present.
pass
Open Graph basics
bonus
2/2
Evidence. Open Graph plus canonical.
pass
llms.txt
2/2
Evidence. Found /llms.txt with content.
pass
llms.txt index
Recommended
2/2
Evidence. llms.txt has content.
pass
llms.txt size and links
Recommended
2/2
Evidence. llms.txt 10280 chars, 52 URL(s).
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
Section llms.txt
bonus
0/1
Evidence. No /docs/llms.txt.
n/a
NLWeb schemamap
bonus
0/1
Evidence. No schemamap (N/A unless you offer NL search).
pass
Trust pages
Recommended
2/2
Evidence. Trust links found.
n/a
Speakable markup
bonus
0/1
Evidence. No SpeakableSpecification (N/A unless voice content).
pass
humans.txt
bonus
1/1
Evidence. humans.txt present.
pass
security.txt
Recommended
1/1
Evidence. RFC 9116 security.txt with Contact.
pass
RSS or Atom feed
1/1
Evidence. Feed link detected.
pass
RSS or Atom document
bonus
1/1
Evidence. Fetched a feed document.
Probed public URLs named in the evidence.
failed
Agent instruction / when-to-use
Required
0/3
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.
failed
Organization schema completeness
Recommended
0/2
Evidence. Organization JSON-LD missing contactPoint and address.
Recommended fix. Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress).
pass
Schema type breadth
Recommended
2/2
Evidence. JSON-LD types beyond Organization/WebSite: SearchAction, EntryPoint.
pass
Content without JavaScript
Required
3/3
Evidence. Raw HTML has H1 and 2023 visible characters without JavaScript.
4. Can an agent integrate with you? 37/100
Whether there is a documented machine door into the product.
pass
OpenAPI / Swagger link
2/2
Evidence. Homepage links mention OpenAPI or Swagger.
Probed homepage + OpenAPI.
failed
Login or docs link
0/3
Evidence. No login/docs/developers link.
Recommended fix. Link to login and developer documentation from the homepage.
n/a
MCP well-known card
0/2
Evidence. No MCP surface (N/A).
n/a
MCP SSE / HTTP hint
0/1
Evidence. No MCP/SSE hint on the homepage.
Probed homepage.
n/a
openapi.json fetchable
0/0
Evidence. OpenAPI linked but not fetchable at common or discovered paths.
Probed OpenAPI.
failed
Webhook or API docs
0/2
Evidence. No webhook/API docs mention.
Recommended fix. Document webhooks and REST/RPC APIs for agents.
n/a
Agent skills index
0/2
Evidence. No agent-skills index (N/A unless you publish skills).
partial
OpenAPI document
Required
1/7
Evidence. OpenAPI probe.
Probed OpenAPI.
Recommended fix. Publish an OpenAPI document at a stable URL. Verify: curl -sI https://digidai.github.io/openapi.json
pass
Public API surface
Recommended
7/7
Evidence. Docs or API paths look callable.
partial
Developer portal
Recommended
1/6
Evidence. No developer portal.
Recommended fix. Offer a self-serve docs hub.
n/a
MCP server
Recommended
0/6
Evidence. MCP probe.
n/a
MCP server card
Recommended
0/2
Evidence. No MCP surface (N/A).
n/a
Agent Skills files
bonus
0/2
Evidence. No SKILL.md surface (N/A).
failed
CLI tool
Recommended
0/3
Evidence. No CLI mention.
Recommended fix. Publish an official CLI.
n/a
GraphQL GET hint
bonus
0/2
Evidence. No GraphQL surface (N/A).
n/a
OpenAPI UI page
bonus
0/1
Evidence. No swagger-ui/redoc page.
n/a
OpenAPI (legacy slot)
0/0
Evidence. Linked but not fetched.
Probed public URLs named in the evidence.
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/3
Evidence. No MCP card to initialize
n/a
MCP server card
Recommended
0/2
Evidence. No MCP surface (N/A).
n/a
REST typed error model
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST versioning / deprecation policy
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST pagination pattern
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST async-job pattern
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST response schema coverage
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
Function calling compatibility
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST batch / bulk endpoint
bonus
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
MCP tool listing
bonus
0/3
Evidence. No public tools/list.
n/a
MCP tool descriptions
bonus
0/3
Evidence. No public tools/list.
n/a
MCP parameter schemas
bonus
0/2
Evidence. No public tools/list.
n/a
MCP tool naming
bonus
0/2
Evidence. No public tools/list.
n/a
MCP tool annotations
bonus
0/2
Evidence. No public tools/list.
n/a
MCP resources exposed
Recommended
0/3
Evidence. No public MCP initialize.
6. Can an agent use you reliably in production? 54/100
Whether errors, idempotency, and limits are visible before a call fails.
partial
Rate limit signal
Recommended
1/2
Evidence. API surface without a rate-limit signal.
Recommended fix. Document or send rate-limit headers on APIs.
partial
Idempotency signal
Recommended
1/3
Evidence. API surface without idempotency notes.
Recommended fix. Document idempotency keys for mutating calls.
partial
Machine-readable errors
Recommended
1/4
Evidence. API surface without a JSON error shape.
Recommended fix. Return a JSON or problem+json error body.
pass
Honest 404
Recommended
2/2
Evidence. Unknown path returned HTTP 404.
pass
Sandbox / test environment
bonus
2/2
Evidence. Docs mention a sandbox or test key.
n/a
Agent onboarding friction
Recommended
0/2
Evidence. No OpenAPI spec; onboarding stays N/A (no live signup probe).
Probed OpenAPI.
n/a
MCP error handling
bonus
0/2
Evidence. No public tools/call surface.
7. Can an agent authenticate to you? 50/100
Whether an agent can obtain access without a human in the loop.
partial
OAuth / OIDC well-known
1/2
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/5
Evidence. No delegated-access surface (N/A).
n/a
OAuth AS metadata
Required
0/3
Evidence. No AS metadata (N/A unless you run an AS).
n/a
PKCE S256
Required
0/2
Evidence. No OAuth metadata to evaluate PKCE.
n/a
OAuth protected resource
Recommended
0/2
Evidence. No OAuth resource metadata (N/A).
n/a
Scoped permissions
Recommended
0/5
Evidence. No named OAuth scopes.
n/a
Scoped permissions
Recommended
0/2
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
auth.md
bonus
0/2
Evidence. No /auth.md (optional).
n/a
auth.md structure
bonus
0/2
Evidence. No /auth.md to grade.
n/a
change-password well-known
bonus
0/1
Evidence. No account door (N/A).
n/a
MCP auth mechanism
bonus
0/2
Evidence. No discovered MCP endpoint to grade auth.
n/a
Agent auth WWW-Authenticate hint
bonus
0/1
Evidence. No documented API path to probe for WWW-Authenticate.
8. Can an agent transact with you? 0/100
Whether an agent can price, pay, or check out on a documented rail.
n/a
x402 payment
bonus
0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
Agentic checkout (ACP)
bonus
0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
ACP delegated payment
bonus
0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
Universal Commerce Protocol
bonus
0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
Machine Payments Protocol
bonus
0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
AP2 - Agent Payments Protocol
bonus
0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
failed
Pricing page
Recommended
0/3
Evidence. No pricing page.
Recommended fix. Publish /pricing.
n/a
pricing.md
bonus
0/2
Evidence. No /pricing.md (optional).
9. Can a user act through an agent? 100/100
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/2
Evidence. No agent-card.json (N/A unless A2A).
pass
Web app manifest
bonus
1/1
Evidence. Web app manifest fetched.
Probed public URLs named in the evidence.
scanner error
Listed on skills.sh
bonus
0/1
Evidence. skills.sh search The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
10. Can an agent operate your website directly? 67/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. Advertised markdown twin but homepage did not negotiate markdown.
Probed homepage.
Recommended fix. Respond to Accept: text/markdown with a markdown body.
pass
/index.md fallback
bonus
1/1
Evidence. Fetched /index.md.
Probed public URLs named in the evidence.
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).
pass
Agent mode view
bonus
1/1
Evidence. mode=agent responded.
Probed public URLs named in the evidence.
n/a
NodeInfo
bonus
0/1
Evidence. No nodeinfo (N/A).
n/a
oEmbed discovery
bonus
0/1
Evidence. No oEmbed (N/A unless embeddable).
pass
Markdown alternate link
bonus
1/1
Evidence. rel=alternate markdown https://digidai.github.io/index.md
Probed public URLs named in the evidence.
failed
Markdown frontmatter metadata
bonus
0/1
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.
n/a
Markdown content negotiation (acceptmarkdown.com)
bonus
0/1
Evidence. Homepage does not negotiate markdown.
Probed homepage.
failed
Agent-UA markdown docs
bonus
0/1
Evidence. Docs host did not serve markdown to GPTBot (HTTP 526, text/plain; charset=utf-8).
Recommended fix. Serve text/markdown to GPTBot (and similar agent UAs) on your docs host.
pass
Accessible document structure
bonus
3/3
Evidence. Homepage HTML has main, nav, H1, and a sane heading order.
Probed homepage.
pass
Code fence validity
bonus
1/1
Evidence. No fenced blocks to unbalance.
partial
llms.txt links resolve
Recommended
1/2
Evidence. 7 real, 1 homepage-shell, 0 dead of 8 sampled links.
Probed homepage.
Recommended fix. Make every link your llms.txt declares resolve to real content, not a homepage shell 200.
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
- vercel.com88.9/100 · AScan them →
- netlify.com84/100 · BScan them →
- render.com81.2/100 · BScan 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.