◎ Discry Score
apache.org.com
infrastructure · API
F
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 98 (A)
Discry your API →
INFRASTRUCTURE · RANK #67 OF 68

apache.org is Not Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the apache.org API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 24/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Fail
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Partial
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Partial
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Fail

Comprehension

55% of score · 12/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Fail
Realistic examplesRunnable, real-world request/response examples.Fail
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Fail
Error-recovery guidanceDocumented failure modes and how to recover from them.Fail
Answer-first formatThe answer leads; preamble does not bury it.Fail
Capability boundariesClear limits — what the API can and cannot do.Fail
Naming consistencyConsistent, predictable naming across endpoints.Fail
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial
Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

  • apache.org is the Apache Software Foundation's foundation/community homepage, not an API. An agent sent to this URL to 'call the Apache API' finds a marketing and governance site — 290+ projects, sponsors, events, and blog posts — with no endpoints, authentication, or reference documentation to act on.
  • No agent-discovery surface exists at the domain root: llms.txt, llms-full.txt, .well-known/mcp.json, and sitemap.xml all return 404, so an agent has no structured entry point to the foundation's resources.
  • One clear positive: robots.txt allows all crawlers (only /websrc is disallowed, with a 4s crawl delay) and places no AI-bot-specific blocks, so GPTBot, ClaudeBot, and peers can freely index the site.
  • The Apache ecosystem is agent-aware even though apache.org itself is not — individual project repos (apache/hbase, apache/groovy-website, apache/fory-site) ship AGENTS.md files, and official Apache MCP servers (Apache ECharts, Apache Sling) are listed on PulseMCP and Glama. None of these represent apache.org itself.
  • Comprehension is near-zero by construction: with no API, there are no endpoint descriptions, code examples, error-recovery guidance, or capability boundaries for an agent to comprehend. The homepage does render as clean, well-nested markdown, which is the only comprehension signal that survives.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Clarify the assessment target: apache.org the foundation homepage is not a scorable API. Redirect agent-readiness scanning to a specific Apache project's docs (e.g. httpd.apache.org, projects.apache.org data feeds, or a project with a real REST API) to get a meaningful score.
  2. 02If the ASF wants the foundation site to be agent-navigable, add an llms.txt at the root that indexes the key destinations already in the nav — Projects Directory, Downloads, Security/vulnerability reporting, Developer Information, and the machine-readable project data at projects.apache.org.
  3. 03Publish or link the existing machine-readable project metadata (projects.apache.org already exposes structured project/release data) from the domain root so an agent can discover the ASF's actual programmatic surface.
  4. 04Add a sitemap.xml at apache.org so crawlers and agents can enumerate foundation pages rather than relying on in-page navigation.
  5. 05Consider a root-level AGENTS.md for the apache.org website repository, mirroring the pattern already adopted by apache/groovy-website and apache/fory-site, to guide agents interacting with the site's source.

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

✕ Error format documented✕ Rate limits documented✕ Pagination documented✕ Idempotency documented

apache.org is the Apache Software Foundation's organizational homepage, not an API product. It documents no authentication, error formats, rate limits, pagination, or idempotency because it exposes no API surface of its own. Machine-readable project data lives on separate subdomains (e.g. projects.apache.org).

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free