apidapp.com is Not Agent-Ready to agents.
Discry independently scored how well an AI agent can discover and understand the apidapp.com API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.
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 · 0/100Comprehension
55% of score · 41/100What we found
- An agent trying to discover this API programmatically finds nothing: no robots.txt, llms.txt, sitemap.xml, OpenAPI spec, AGENTS.md, or .well-known/mcp.json — every discovery signal returns 404, producing a Discovery score of 0.
- The apex domain (apidapp.com) does not resolve at all — the site only exists at www.apidapp.com, so an agent following the registered domain would fail DNS before ever reaching documentation.
- 'Documentation' is a single static marketing landing page plus an APILayer marketplace tile; the marketplace 'docs' link simply redirects back to the homepage, so there is no endpoint reference, no auth guide, and no error catalog.
- The one bright spot: the lone code example uses realistic values (real-looking wallet addresses, Polygon chain_id 137, IPFS/callback URLs) and consistent snake_case naming — an agent that only needs to mint one NFT could copy-paste it.
- The site advertises 20 blockchains and 13 protocols but documents exactly one flow (ERC-721 mint on Polygon), so an agent cannot learn what most of the advertised surface actually does.
What to change
Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.
- 01Publish real documentation with a per-endpoint reference (method, URL, purpose, parameters, response schema) for the full advertised surface — right now an agent can only see one example call.
- 02Add the discovery basics an agent looks for first: a robots.txt that allows AI crawlers, a sitemap.xml, and an llms.txt summarizing the API and linking to the endpoint docs — all are currently 404 and each is a quick win.
- 03Publish and link a machine-readable OpenAPI/Swagger spec so agents can generate clients and understand the schema without scraping a marketing page.
- 04Document error responses with codes, machine-parseable JSON format, and recovery guidance, plus rate limits and pagination — none of these execution characteristics are documented today.
- 05Fix the apex domain so apidapp.com resolves (redirect to www), since an agent given the bare domain currently fails DNS resolution entirely.
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.
Execution characteristics are almost entirely undocumented. A single homepage example shows Bearer-token auth (via a requested access key) on a beta endpoint; there is no documented error format, no rate limits, no pagination, and no idempotency guidance.