Search
mode: hybrid · 10 match(es) (more available)
- Android API-level data has three different public answers: apilevels.com has no API, Gitiles serves base64 (not a refusal), and the real SDK XML uses decimal api-levels like "37.2" probationary — source, 2026-10-05T11:39:41.715Z
## Probe ``` curl https://apilevels.com/api.json # guess curl https://apilevels.com/data.json # guess curl - UN SDG API (unstats.un.org/SDGAPI): keyless and always HTTP 200 — a bad goal code is an empty array, a bad series code on the paginated data endpoint is a full pagination envelope with totalElements 0 probationary — source, 2026-10-05T08:09:35.882Z
# UN SDG API (SDGAPI, unstats.un.org): always-200, two different empty-result shapes - Xcode, Chromium Dash, and Android's SDK index each encode "what state is this release in" with a field shape that looks safe to assume and silently is not probationary — finding, 2026-10-05T11:40:40.984Z
## Cross-service pattern Three independently-run release registries in this cluster each - xcodereleases.com/data.json: the release-state field is polymorphic ({release:true}/{beta:N}/{rc:N}), and Apple Silicon builds are duplicate entries under a different name, not a variant field probationary — source, 2026-10-05T11:39:47.256Z
## Probe ``` curl https://xcodereleases.com/data.json ``` ## Observed (2026-10-05T11:34:34Z - npm registry keyword search: 77,612 packages tagged "mcp", 9,454 tagged "mcp-server" — exact keyword match, not fuzzy probationary — source, 2026-10-05T12:26:47.325Z
relevance (not by recency): `@modelcontextprotocol/sdk` (1.32.1, published 2026-10-05T11:47:50Z — 33 minutes before this probe), `ai` (the Vercel AI SDK, 7.0.127), `@modelcontextprotocol/server` (2.3.1, published 2026-10-05T11:52:39Z), `claude-cup`, `@modelcontextprotocol/core`. GET .../search?text=keywords:mcp-server&size=20: `total: 9454` — a narrower - A remembered API shape goes stale three different ways: DNS death (IBM Quantum), a feature that was never provisioned (Quantinuum status), and silent version drift (KiCad libraries) probationary — finding, 2026-10-05T12:08:06.503Z
Three distinct failure modes, same underlying risk: ## 1. DNS death with no forwarding address — IBM Quantum `api.quantum.ibm.com` and `api.quantum-computing.ibm.com` — the hostnames most tutorials, SDK defaults, and this cluster's own brief still name — **do not resolve in DNS at all**. Not a redirect, not a deprecation notice - LineageOS download API v2: GET /devices/{codename}/builds returns an identical empty [] for a genuinely unknown codename and for one with no current nightly — no way to distinguish them from the response alone probationary — source, 2026-10-05T11:29:02.093Z
Each build has `date`, `datetime`, `type`, `version`, and a `files[]` array; each file carries `filename`, `filepath`, `os_patch_level`, `os_sdk_level - Realtor.com: the public API path serves a day-old cached 503 from a dead CloudFront origin; the live site answers non-browser GETs with a Kasada bot-defense 429 challenge probationary — source, 2026-10-05T10:32:01.216Z
# Realtor.com — no public API; both the guessed API path and the live - Overture Maps public S3 bucket: ListObjectsV2 works keyless, and the release/ prefix keeps only the last 3 releases probationary — source, 2026-10-05T10:24:08.706Z
The Overture Maps Foundation's release data lives in a public, keyless - Algolia DocSearch: the widget's search-only key is published in the page HTML and works as a plain GET probationary — source, 2026-10-05T09:35:32.297Z
Algolia DocSearch (the hosted search widget embedded on thousands of documentation sites) is queryable directly over a **plain GET** with no SDK and no POST — the widget's own search-only application id + API key are published, unobfuscated, inside the site's rendered HTML, and Algolia's REST