ora.ai
Journey
90.9/ 100
A · Strong technical baseline
Waymark scored ora.ai 90.9/100 (A) on 26 Aug 2026.
ora.ai is mostly ready. Discovery is the strongest layer, and Access is the open one. Next: agent instruction / when-to-use.
FindStrong
20/20
21 of 21 checks passed
DoorMixed
24.2/30
32 of 43 checks passed
ToolsStrong
37.6/40
30 of 33 checks passed
Pay
N/A
No cart or pay rail — out of the denominator.
Group by
1. Can an agent discover and trust you? 100/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.
pass
Well-known AI catalog
1/1
Evidence. Found /.well-known AI catalog JSON.
Probed well-known paths.
pass
AGENTS.md
1/1
Evidence. Found /agents.md.
pass
robots.txt AI policy
Required
2/2
Evidence. Named AI crawlers: CCBot, ByteSpider, anthropic-ai, GPTBot, ClaudeBot, Google-Extended.
pass
Sitemap for agents
Recommended
2/2
Evidence. Sitemap document fetched.
Probed sitemap.
pass
HTTP Link header
bonus
1/1
Evidence. Link: </sitemap.xml>; rel="sitemap", </index.md>; rel="alternate"; type="text/markdown", </api/openapi.json>; rel="service-desc", </.well-known/api-catalog>; rel="htt
Probed well-known paths + sitemap + OpenAPI.
pass
ai-plugin.json
bonus
1/1
Evidence. ai-plugin.json present.
pass
API catalog linkset
bonus
2/2
Evidence. api-catalog found.
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://registry.modelcontextprotocol.io/v0/servers?search=ora.
Probed public URLs named in the evidence.
pass
Package homepage match
bonus
1/1
Evidence. npm package homepage matches ora.ai.
Probed homepage.
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? 42/100
Whether crawlers and signed bots are allowed through rather than blocked at the door.
failed
AI crawlers not blanket-blocked
0/2
Evidence. robots.txt Disallow: / for * or common AI bots.
Probed robots.txt.
Recommended fix. Avoid Disallow: / for GPTBot, ClaudeBot, PerplexityBot unless intentional.
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.
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.
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? 87/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 7700 chars, 45 URL(s).
pass
llms-full.txt
bonus
1/1
Evidence. llms-full.txt present.
pass
Section llms.txt
bonus
1/1
Evidence. Fetched /docs/llms.txt.
Probed public URLs named in the evidence.
pass
NLWeb schemamap
bonus
1/1
Evidence. schemamap directive in robots.txt.
Probed robots.txt.
pass
Trust pages
Recommended
2/2
Evidence. Trust links found.
pass
Speakable markup
bonus
1/1
Evidence. Speakable markup found.
n/a
humans.txt
bonus
0/1
Evidence. No /humans.txt (optional).
failed
security.txt
Recommended
0/1
Evidence. No /.well-known/security.txt Contact.
Probed well-known paths.
Recommended fix. Publish /.well-known/security.txt with a Contact field.
failed
RSS or Atom feed
0/1
Evidence. No RSS/Atom link.
Recommended fix. Expose an RSS or Atom feed for machine subscribers.
n/a
RSS or Atom document
bonus
0/1
Evidence. No /feed or /rss.xml document.
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.
pass
Organization schema completeness
Recommended
2/2
Evidence. Organization JSON-LD includes contactPoint and address.
pass
Schema type breadth
Recommended
2/2
Evidence. JSON-LD types beyond Organization/WebSite: SoftwareApplication, Offer, SearchAction, EntryPoint, Service, SpeakableSpecification.
pass
Content without JavaScript
Required
3/3
Evidence. Raw HTML has H1 and 1981 visible characters without JavaScript.
4. Can an agent integrate with you? 91/100
Whether there is a documented machine door into the product.
failed
OpenAPI / Swagger link
0/2
Evidence. No OpenAPI/Swagger link in HTML.
Probed OpenAPI.
Recommended fix. Link to an OpenAPI or Swagger document from the homepage.
pass
Login or docs link
3/3
Evidence. Login or developer docs link found.
pass
MCP well-known card
2/2
Evidence. MCP server card found under .well-known.
Probed well-known paths.
pass
MCP SSE / HTTP hint
1/1
Evidence. Page mentions MCP or SSE transport.
n/a
openapi.json fetchable
0/0
Evidence. Fetched OpenAPI or Swagger document.
Probed OpenAPI.
pass
Webhook or API docs
2/2
Evidence. Webhook or API docs mention found.
pass
Agent skills index
2/2
Evidence. Skills index or mention found.
pass
OpenAPI document
Required
5/7
Evidence. OpenAPI probe.
Probed OpenAPI.
pass
Public API surface
Recommended
7/7
Evidence. Docs or API paths look callable.
pass
Developer portal
Recommended
6/6
Evidence. Developer hub found.
pass
MCP server
Recommended
6/6
Evidence. https://mcp.ora.ai/ initialize 200
Probed public URLs named in the evidence.
pass
MCP server card
Recommended
2/2
Evidence. MCP card JSON found.
pass
Agent Skills files
bonus
2/2
Evidence. Skills file or index found.
pass
CLI tool
Recommended
3/3
Evidence. CLI mention found.
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. OpenAPI/Swagger fetched.
Probed OpenAPI.
5. Is your integration well-built? 100/100
Whether the integration surface is complete enough to call with confidence.
pass
MCP initialize
Required
3/3
Evidence. initialize HTTP 200 at https://ora.ai/api/mcp
Probed public URLs named in the evidence.
pass
MCP server card
Recommended
2/2
Evidence. MCP card JSON found.
pass
REST typed error model
Recommended
1/1
Evidence. OpenAPI documents a typed error / problem+json shape.
Probed OpenAPI.
pass
REST versioning / deprecation policy
Recommended
1/1
Evidence. OpenAPI shows a version path, header, or deprecation signal.
Probed OpenAPI.
pass
REST pagination pattern
Recommended
1/1
Evidence. OpenAPI documents a cursor/page pagination shape.
Probed OpenAPI.
pass
REST async-job pattern
Recommended
1/1
Evidence. OpenAPI documents 202 / async-job polling.
Probed OpenAPI.
pass
REST response schema coverage
Recommended
1/1
Evidence. Typed 200 schemas on ~16 operations.
pass
Function calling compatibility
Recommended
1/1
Evidence. 25 operationIds and descriptions look function-calling friendly.
n/a
REST batch / bulk endpoint
bonus
0/1
Evidence. No batch/bulk endpoint (N/A).
pass
MCP tool listing
bonus
3/3
Evidence. tools/list HTTP 200 at https://mcp.ora.ai/, 13 tool(s).
Probed public URLs named in the evidence.
pass
MCP tool descriptions
bonus
3/3
Evidence. 13/13 tools have descriptions ≥20 chars.
pass
MCP parameter schemas
bonus
2/2
Evidence. 13/13 tools have inputSchema.
pass
MCP tool naming
bonus
2/2
Evidence. 13/13 tools use descriptive names.
pass
MCP tool annotations
bonus
2/2
Evidence. 13/13 tools have behavioral annotations.
pass
MCP resources exposed
Recommended
3/3
Evidence. resources/list returned 7 resource(s).
6. Can an agent use you reliably in production? 87/100
Whether errors, idempotency, and limits are visible before a call fails.
pass
Rate limit signal
Recommended
2/2
Evidence. Rate-limit or retry signal found.
partial
Idempotency signal
Recommended
1/3
Evidence. API surface without idempotency notes.
Recommended fix. Document idempotency keys for mutating calls.
pass
Machine-readable errors
Recommended
4/4
Evidence. JSON/problem error shape found.
pass
Honest 404
Recommended
2/2
Evidence. Unknown path returned HTTP 404.
n/a
Sandbox / test environment
bonus
0/2
Evidence. Docs do not mention sandbox/test keys (N/A).
pass
Agent onboarding friction
Recommended
2/2
Evidence. Docs describe self-serve keys or a free/trial path.
pass
MCP error handling
bonus
2/2
Evidence. Bad tools/call returned a structured JSON-RPC error.
7. Can an agent authenticate to you? 81/100
Whether an agent can obtain access without a human in the loop.
pass
OAuth / OIDC well-known
2/2
Evidence. OAuth or OIDC discovery document found.
pass
OAuth 2.0 surface
Required
5/5
Evidence. Authorization or token endpoint in discovery.
pass
OAuth AS metadata
Required
3/3
Evidence. AS or OIDC metadata document fetched.
Probed public URLs named in the evidence.
failed
PKCE S256
Required
0/2
Evidence. Metadata lacks S256 PKCE.
Recommended fix. Advertise S256 in code_challenge_methods_supported.
failed
OAuth protected resource
Recommended
0/2
Evidence. AS present but no resource metadata.
Recommended fix. Publish RFC 9728 oauth-protected-resource if APIs are OAuth-gated.
pass
Scoped permissions
Recommended
5/5
Evidence. Named scopes found.
n/a
Scoped permissions
Recommended
0/2
Evidence. No OAuth2 security schemes with scopes (API-key-only is N/A).
pass
auth.md
bonus
2/2
Evidence. Fetched /auth.md.
Probed public URLs named in the evidence.
pass
auth.md structure
bonus
2/2
Evidence. auth.md has walkthrough structure (discover, register, claim, revoc, error, agent_auth).
failed
change-password well-known
bonus
0/1
Evidence. Login surface without /.well-known/change-password.
Probed well-known paths.
Recommended fix. If users have passwords, serve /.well-known/change-password.
pass
MCP auth mechanism
bonus
2/2
Evidence. MCP initialize succeeded (public or session).
n/a
Agent auth WWW-Authenticate hint
bonus
0/1
Evidence. Documented API path returned HTTP 405, not 401.
8. Can an agent transact with you? 100/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).
pass
Pricing page
Recommended
3/3
Evidence. Fetched /pricing.
Probed public URLs named in the evidence.
pass
pricing.md
bonus
2/2
Evidence. Fetched /pricing.md.
Probed public URLs named in the evidence.
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).
pass
A2A agent card
Required
2/2
Evidence. Agent card JSON found.
n/a
Web app manifest
bonus
0/1
Evidence. No web app manifest (N/A).
n/a
Listed on skills.sh
bonus
0/1
Evidence. No official skills.sh org for this brand; community listings are N/A.
10. Can an agent operate your website directly? 77/100
Whether an agent can read and operate the site itself when there is no API or MCP.
pass
Markdown negotiation
bonus
1/1
Evidence. Accept markdown returned text/markdown; charset=utf-8.
pass
/index.md fallback
bonus
1/1
Evidence. Fetched /index.md.
Probed public URLs named in the evidence.
pass
WebMCP page tools
bonus
1/1
Evidence. WebMCP / modelContext mention.
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).
n/a
Markdown alternate link
bonus
0/1
Evidence. No rel=alternate type=text/markdown.
pass
Markdown frontmatter metadata
bonus
1/1
Evidence. Markdown opens with title plus metadata frontmatter.
pass
Markdown content negotiation (acceptmarkdown.com)
bonus
1/1
Evidence. Vary includes Accept (Accept, accept-encoding).
pass
Agent-UA markdown docs
bonus
1/1
Evidence. GPTBot Accept: text/markdown returned text/plain; charset=utf-8.
partial
Accessible document structure
bonus
1/3
Evidence. Landmarks partial (main=true nav=true h1=true skip=true).
Recommended fix. Give the homepage a main region, nav, H1, and a heading order that does not skip levels.
pass
Code fence validity
bonus
1/1
Evidence. Code fences balanced (``` 4, ~~~ 0).
partial
llms.txt links resolve
Recommended
1/2
Evidence. 3 real, 0 homepage-shell, 5 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
- superset.sh90.7/100 · AScan them →
- waymark.genedai.me87.2/100 · AScan them →
- kernel.sh86.6/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.