◎ Discry Score
agave games.com
commerce · API
F
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 95 (A)
Discry your API →
COMMERCE · RANK #21 OF 21

Agave Games is Not Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the Agave Games 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 · 19/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.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Fail
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Partial

Comprehension

55% of score · 0/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.Fail
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Fail
Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

  • agavegames.com is not an API — it is a consumer mobile-game studio's marketing and careers website (Webflow-hosted). An agent looking for a programmable interface would find only company pages: home, life-at-agave, careers, and legal/privacy notices.
  • There is no public API, developer portal, OpenAPI spec, SDK, or endpoint reference anywhere on the domain. Every documentation-comprehension signal fails because there is no documentation to comprehend.
  • The only positive discovery signal is a permissive robots.txt (a single Sitemap directive, no AI-bot blocks) and a valid sitemap.xml — but the sitemap lists marketing pages only, no docs.
  • No AGENTS.md, no .well-known/mcp.json, no llms.txt, and no MCP-registry listing exist. Web search for an Agave Games API returns only unrelated companies (a construction API and an HR/hiring API, both at different domains).
  • For any agent GTM or directory purpose this domain is a non-target: it exposes no machine-consumable surface and nothing to integrate with.

What to change

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

  1. 01If (and only if) Agave Games intends to expose a developer or partner API in future, publish an OpenAPI 3.x spec at a discoverable path (e.g. /openapi.json) — this is the single highest-weighted discovery signal and is currently entirely absent.
  2. 02Add an llms.txt at the domain root summarizing what the company/product offers and linking to any structured resources, so agents can orient without scraping Webflow marketing HTML.
  3. 03Only pursue the above if a real programmatic surface exists; as a consumer game studio with no public API, the practical recommendation is that this domain is out of scope for agent-readiness and should not be treated as an API target.
  4. 04If the goal is agent discoverability of the games themselves, the relevant surfaces are the app-store listings (Google Play / App Store), not agavegames.com.

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

No API, developer portal, or execution documentation exists. agavegames.com is a Webflow marketing and careers site for a mobile game studio — there is nothing for an agent to authenticate against, call, or parse.

See your own Discry Score.

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

Discry your API — free