◎ Discry Score
alertersystem.com.com
communication · API
F
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 98 (A)
Discry your API →
COMMUNICATION · RANK #24 OF 24

alertersystem.com is Not Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the alertersystem.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.

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 · 12/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial
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.Fail
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.Partial
Capability boundariesClear limits — what the API can and cannot do.Fail
Naming consistencyConsistent, predictable naming across endpoints.Pass
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

  • An agent looking for this API today finds nothing: alertersystem.com returns NXDOMAIN — the domain no longer resolves. No robots.txt, llms.txt, sitemap, or live documentation exists, and the service appears defunct.
  • The only surviving artifact is a stale OpenAPI 3.0 spec (v1.6.0, last updated March 4, 2023) mirrored in the third-party apis.guru registry — 100 paths, API Platform-generated, OAuth2. An agent can retrieve the schema but cannot reach the API (server URL is a bare '/').
  • The one agent-friendly quality is machine consistency: the spec uses uniform snake_case property names and leads each operation with method/path, so what little exists is parseable.
  • Endpoint descriptions are generic auto-generated boilerplate ('Retrieves the collection of AlertLog resources') with no task context — an agent cannot tell what a call actually accomplishes.
  • There are no multi-step workflow guides, no error-recovery guidance, no MCP registry listing (Glama/Smithery/PulseMCP), and no AGENTS.md anywhere.

What to change

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

  1. 01Restore DNS and a live site — nothing else matters while alertersystem.com returns NXDOMAIN; an agent cannot discover or call the API at all in its current state.
  2. 02Publish a self-hosted, current OpenAPI spec at a stable URL. The only spec in circulation is a 3-year-old third-party mirror whose server is a meaningless relative '/'.
  3. 03Add an llms.txt at the domain root summarizing core alerting capabilities and linking the spec and the OAuth flow, so agents get a right-sized entry point.
  4. 04Replace API Platform's auto-generated summaries with task-oriented descriptions (e.g. 'Send an alert to a configured channel') and add 2-3 multi-step quickstart guides covering real use cases.
  5. 05List an MCP server on Glama or Smithery and add explicit error-recovery guidance (what to do on 4xx/429) to the docs.

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.

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

Execution characteristics survive only in the archived OpenAPI spec: OAuth2 security, Hydra-style error responses, and Hydra pagination parameters are machine-declared. None of it can be verified because the API's domain no longer resolves (NXDOMAIN) and there is no live documentation.

See your own Discry Score.

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

Discry your API — free