◎ Discry Score
blue sky analytics.com
analytics · API
F
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 92 (A)
Discry your API →
ANALYTICS · RANK #29 OF 29

Blue Sky Analytics is Not Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the Blue Sky Analytics 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 · 0/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.Fail
SitemapA sitemap so agents can enumerate the docs surface.Fail

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

  • The domain blueskyhq.io no longer resolves — DNS lookups return ENOTFOUND from both direct resolution and Firecrawl. An agent attempting to discover or call this API today reaches a dead end before any documentation loads.
  • Blue Sky Analytics is confirmed no longer operating: its accelerator, Unreasonable Group, states the company 'is no longer operating.' This is a defunct API, not merely a poorly-documented one.
  • The former developer portal (developer.blueskyhq.io) and Climate Data Hub (blueskyhq.io/data-hub) are both unreachable — every discovery signal (robots.txt, llms.txt, OpenAPI spec, sitemap) is inaccessible.
  • No MCP registry listing exists on Glama, Smithery, or PulseMCP, so there is no fallback surface an agent could use to reach the API even indirectly.
  • Historically the product offered a real environmental/geospatial dataset API (API-key auth, 300 free calls/month, spatiotemporal endpoints), but that has no bearing on present-day agent-readiness — the service is gone.

What to change

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

  1. 01Remove Blue Sky Analytics from the active Discry Directory or flag it as defunct — the domain is dead and the company has ceased operations, so it cannot score on agent-readiness.
  2. 02If a successor entity or archived API exists, re-scan against the live domain; there is nothing to assess at blueskyhq.io today.
  3. 03For directory hygiene, add a pre-scan liveness check (DNS + HTTP 200 on the base domain) so defunct APIs are auto-flagged rather than scored as F on documentation grounds.

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 execution documentation is accessible. The domain blueskyhq.io no longer resolves (DNS ENOTFOUND) and Blue Sky Analytics is confirmed to be no longer operating. Historical references indicate an API-key-authenticated environmental dataset API (300 free calls/month, spatiotemporal endpoints), but none of it is reachable today.

See your own Discry Score.

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

Discry your API — free