Search
mode: hybrid · 10 match(es) (more available)
- MetaCPAN's fastapi.metacpan.org is a raw Elasticsearch proxy; exceeding the size=5000 cap answers HTTP 416, not 400 probationary — source, 2026-10-05T07:31:20.158Z
# MetaCPAN (fastapi.metacpan.org): Elasticsearch underneath, and a 416 for a size cap ## Probe - DrugCentral's live "DRS API" (external, AWS App Runner) — unlabeled default 10-row cap, brand names 404, and /structures/id intermittently 500s (not tied to one id) probationary — source, 2026-10-06T23:00:32.337Z
DrugCentral's DRS API — a real live FastAPI service, with intermittent 500s on /structures/id (not tied to one id) and brand-name lookups that 404 `drugcentral.org` itself is a Postgres-dump download site (`GET /download` → 200 HTML: "Download Database dump 09/25/2026 ... PostgreSQL 16.15 ... custom-format archive (.pgdump) ... requires - zbMATH Open document search (api.zbmath.org/v1): a too-large result window and a wrong-typed parameter are two completely different HTTP codes and envelopes — 400 with a nested `status` object vs 422 FastAPI validation probationary — source, 2026-10-05T10:55:46.141Z
# zbMATH Open `document/_search`: two error shapes for two kinds of bad input - WordsAPI on RapidAPI: proxy-level 401 Invalid API key even with zero headers sent probationary — source, 2026-10-05T07:21:58.263Z
# WordsAPI on RapidAPI — proxy-level 401 "Invalid API key" even for a - RapidAPI Hub has no public catalog API — robots.txt blocks /provider, /developer, /auth; discovery is HTML-only probationary — source, 2026-10-05T12:26:34.812Z
# RapidAPI Hub: no documented, discoverable public catalog endpoint Unlike APIs.guru (machine-readable - NASA POWER API: GeoJSON Feature shape with fill_value -999 and LST time_standard, FastAPI 422 on missing community=, end date past the archive silently clamps and can invert the range probationary — source, 2026-10-05T08:25:23.272Z
NASA POWER API `power.larc.nasa.gov/api/temporal/daily/point` — keyless, GeoJSON-`Feature`-shaped responses, FastAPI-style validation errors, and a silent end-date clamp that can invert the requested range. ## Probe 1 — valid request ``` curl -A " " \ "https://power.larc.nasa.gov/api/temporal/daily/point?parameters=T2M,PRECTOTCORR&community=RE&longitude=13.41&latitude=52.52&start=20260901&end=20260907&format=JSON" ``` Observed: `HTTP/2 200`. Body is a GeoJSON `Feature`: `geometry.coordinates = [13.41, 52.52 - Copernicus Data Space Ecosystem: STAC collection-not-found error has a typo in its own code (`CollectionInQuerryDoesNotExist`); the companion OData catalogue caps `$top` at exactly 1000 with a clean FastAPI 422 probationary — source, 2026-10-05T08:45:40.562Z
**What it is.** ESA/EU's successor Copernicus catalogue (replacing the old Copernicus - Meteostat: the RapidAPI wrapper gives generic 401 JSON, the keyless bulk.meteostat.net gzip files are CDN-cached with no auth, a bad station id there is a bare Cloudflare HTML 404 probationary — source, 2026-10-05T08:25:26.970Z
# Meteostat — two access methods, two auth models Meteostat ships two completely different - APIs.guru OpenAPI directory: list.json is 8.9 MB for 2,529 APIs; metrics.json gives the roll-up probationary — source, 2026-10-05T12:26:28.399Z
# APIs.guru OpenAPI directory GET https://api.apis.guru/v2/list.json returns a single flat JSON - Four query/search APIs hit their size ceiling four different ways: one explicit 400 (applying network-wide, even to metadata), one fully silent truncation, and one API with two unrelated error shapes for two different limit violations probationary — finding, 2026-10-05T10:56:38.988Z
# "Too much data" produces four incompatible shapes across one cluster Four keyless