--- title: "Waymark report for llamaindex.ai" canonical: "https://waymark.genedai.me/score/llamaindex.ai" last-updated: "2026-08-24T02:21:23.330Z" --- # Waymark report for llamaindex.ai Waymark scored llamaindex.ai 54.2/100 (C) on 24 Aug 2026. Score: 54.2/100 — Blockers remain Scanned: 2026-08-24T02:21:23.330Z Canonical report: https://waymark.genedai.me/score/llamaindex.ai ## Layer breakdown - Discovery: 5.8/20 (4 of 16 eligible checks passed) - Access: 15.8/30 (10 of 21 eligible checks passed) - Usability: 27.1/40 (7 of 12 eligible checks passed) - Payments: N/A (excluded from the denominator) ## Findings ### 1. XML sitemap - Layer: discovery - Result: failed - Evidence: No sitemap.xml. - Recommended fix: Add /sitemap.xml and reference it from robots.txt. ### 2. llms.txt - Layer: discovery - Result: failed - Evidence: llms.txt status 404. - Recommended fix: Add /llms.txt describing the site for language models. ### 3. AGENTS.md - Layer: discovery - Result: failed - Evidence: agents.md status 404. - Recommended fix: Publish /agents.md with agent-oriented usage notes. ### 4. 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. ### 5. JSON-LD structured data - Layer: access - Result: failed - Evidence: No JSON-LD on the homepage. - Recommended fix: Add JSON-LD (Organization, WebSite, or SoftwareApplication). ### 6. OpenAPI / Swagger link - Layer: access - Result: failed - Evidence: No OpenAPI/Swagger link in HTML. - Recommended fix: Link to an OpenAPI or Swagger document from the homepage. ### 7. RSS or Atom feed - Layer: access - Result: failed - Evidence: No RSS/Atom link. - Recommended fix: Expose an RSS or Atom feed for machine subscribers. ### 8. 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. ### 9. 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. ### 10. 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. ### 11. Sitemap for agents - Layer: discovery - Result: failed - Evidence: No sitemap. - Recommended fix: Publish /sitemap.xml. ### 12. llms.txt index - Layer: discovery - Result: failed - Evidence: Missing /llms.txt. - Recommended fix: Add a markdown index at /llms.txt. ### 13. llms-full.txt - Layer: discovery - Result: failed - Evidence: llms-full.txt status 404. - Recommended fix: Optionally publish /llms-full.txt for one-shot ingest. ### 14. 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. ### 15. JSON-LD entities - Layer: access - Result: failed - Evidence: No JSON-LD. - Recommended fix: Embed Organization, Product, Offer, SoftwareApplication, or FAQPage. ### 16. Markdown negotiation - Layer: access - Result: failed - Evidence: Homepage did not negotiate markdown. - Recommended fix: Respond to Accept: text/markdown with a markdown body. ### 17. /index.md fallback - Layer: access - Result: failed - Evidence: index.md status 404. - Recommended fix: Serve a markdown homepage at /index.md. ### 18. MCP Apps UI hint - Layer: usability - Result: failed - Evidence: No MCP Apps hint (N/A unless you return UI). - Recommended fix: If you return UI, declare io.modelcontextprotocol/ui resources. ### 19. ai-plugin.json - Layer: discovery - Result: failed - Evidence: No /.well-known/ai-plugin.json. - Recommended fix: Optionally publish a plugin-style capability manifest. ### 20. security.txt - Layer: access - Result: failed - Evidence: No /.well-known/security.txt Contact. - Recommended fix: Publish /.well-known/security.txt with a Contact field. ### 21. 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. ### 22. llms.txt size and links - Layer: discovery - Result: failed - Evidence: No llms.txt to score. - Recommended fix: Keep /llms.txt over ~200 characters with absolute URLs to docs. ### 23. Rate limit signal - Layer: usability - Result: partial - Evidence: API surface without a rate-limit signal. - Recommended fix: Document or send rate-limit headers on APIs. ### 24. Idempotency signal - Layer: usability - Result: partial - Evidence: API surface without idempotency notes. - Recommended fix: Document idempotency keys for mutating calls. ### 25. Machine-readable errors - Layer: usability - Result: partial - Evidence: API surface without a JSON error shape. - Recommended fix: Return a JSON or problem+json error body. ### 26. OpenAPI document - Layer: access - Result: failed - Evidence: OpenAPI probe. - Recommended fix: Publish an OpenAPI document at a stable URL. ### 27. CLI tool - Layer: usability - Result: failed - Evidence: No CLI mention. - Recommended fix: Publish an official CLI. ### 28. Package homepage match - Layer: discovery - Result: failed - Evidence: No npm package homepage matching llamaindex.ai. - Recommended fix: Publish an official package 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.