INFRASTRUCTURE · RANK #47 OF 73
apigee.local is Murky to agents.
Discry independently scored how well an AI agent can discover and understand the apigee.local API from what’s public — measuring discovery and comprehension separately, not a single blended number.
Familiarity 20% · what a model knew before reading the docs
Discovery
32 / 100OpenAPI specno publicly accessible spec foundFail
llms.txtnot presentFail
llms-full.txtnot presentFail
AGENTS.mdnot found in repoFail
.well-known/mcp.jsonnot presentFail
MCP registrysmithery match for "google"Pass
robots.txt AI directivesparsed AI-bot rulesPass
Sitemapincludes docs pagesPass
Comprehension
47 / 100Factual recall1/2 passed
Request construction1/2 passed
Absence honesty1/1 passed
Where agents fail
What HTTP header (exact header name) must carry the API credential on requests to this API? — 3/3 runs failed
Produce the exact HTTP request to list this account's existing resources. Output the method, path, required headers, and body. — 3/3 runs failed
See your own Discry result.
Drop your API docs URL. See what an agent sees — in 60 seconds, free.