docs.celestia.org
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
docs.celestia.org
Preparing the stored Is Agentic score
docs.celestia.org
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Blocked
Weighted across 12 applicable checks
Blocked
Weighted across 9 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Verify that major agent User-Agents can reach the homepage. If your WAF or bot rules block them, remove or narrow the blocking rule. Add an allow rule only when your security setup denies them by default.
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
Add a valid XML sitemap at /sitemap.xml listing all indexable URLs. Include lastmod dates and keep it under 50MB.
Checks are grouped by relevance for Docs & content sites.
Homepage blocked by WAF/security challenge - content not accessible to agents
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass, so this is not proof agents are blocked - but unverified agents will not get through.
How to pass
Verify that major agent User-Agents can reach the homepage. If your WAF or bot rules block them, remove or narrow the blocking rule. Add an allow rule only when your security setup denies them by default.
Homepage https://docs.celestia.org does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "none")
How to pass
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
No sitemap found
How to pass
Add a valid XML sitemap at /sitemap.xml listing all indexable URLs. Include lastmod dates and keep it under 50MB.
Homepage blocked by WAF - cannot check structured data
How to pass
Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
Homepage blocked by WAF - cannot check metadata
How to pass
Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
No trust anchor pages found with sufficient content (About, Contact, Privacy)
How to pass
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
ARD catalog valid at /.well-known/ard.json (spec 1.0) - 1/1 entries
Valid AI Catalog at /.well-known/ai-catalog.json (spec 1.0) - 1/1 entries
All 1 entries valid with domain-anchored urn:air identifiers (catalog at /.well-known/ard.json)
Agent found 2 pages by name but no recognizable developer-resource type. Found on site but absent from this search sample: API docs. Not found in this search sample: OpenAPI spec, auth docs, SDK documentation
How to pass
Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
NPM package found: @celestia-island/hikari - "Hikari Vue 3 component library — production-grade UI components based on shittim-chest design system"
Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 1 skill(s)
Index v0.2.0 conformant; verified SHA-256 of "celestia" (skill-md)
Found the llms.txt at https://docs.celestia.org/llms.txt.
The llms.txt is well-formatted: 102 lines with markdown links, 7,268 characters in total.
Agent Skill "celestia" says when to use it at https://docs.celestia.org/.well-known/agent-skills/celestia/SKILL.md - section "## When to use this skill"
Code fences balanced across 1 markdown document
api-catalog has 2 item(s) but content-type is application/octet-stream (expected application/linkset+json)
How to pass
Publish an API catalog at /.well-known/api-catalog per RFC 9727. Serve it with Content-Type: application/linkset+json;profile="https://www.rfc-editor.org/info/rfc9727" and include a 'linkset' array with item entries pointing to your OpenAPI specs and service descriptions.
Homepage blocked by WAF - cannot discover REST API endpoints. GraphQL endpoint at https://docs.celestia.org/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7.
All 8 requirements that apply are met.
Same organization: the ARD catalog host is "Celestia docs", poppy.json names "Celestia".
How to pass
Keep poppy.json consistent with your other agent surfaces: list the same MCP server and organization as your ARD catalog (/.well-known/ard.json), name the same OAuth issuer that your protected-resource metadata lists in authorization_servers, and, when one issuer serves both PAP and auth.md, list every grant both protocols send to its token endpoint in grant_types_supported. Publish a poppy.json naming the same issuer on every domain listed in poppy_domains, and point every 401 at the same resource_metadata URL. Spec: https://personalagentprotocol.org/docs/spec
CLI package found on npm: @celestia-project/create
SDK package found only in npm
How to pass
Publish official SDK packages across multiple language ecosystems (npm, PyPI, Go modules, RubyGems). Auto-generate them from your OpenAPI spec using tools like openapi-generator. For each package set the project URL or homepage to your product domain (package.json repository/homepage, PyPI Home-Page or project_urls, RubyGems homepage_uri) - this is how agents verify the package is your official SDK.
NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET)
What does docs.celestia.org do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does docs.celestia.org do and who is it for? Explain it back to me.
26 steps3 reasoning steps1 search
The agent satisfied the task by assembling a comprehensive explanation of Celestia from documentation fetches and supplementary web research. The site's docs were well-structured and machine-readable (llms.txt, markdown exports, structured pages), but required significant assembly work — the agent had to fetch 15+ pages across Learn, Build, and Operate sections, plus conduct external web searches to answer comparative and pricing questions that the docs alone did not directly address. Navigation was functional but fragmented; the site lacked a single executive summary or alternatives comparison page.