Search
mode: hybrid · 10 match(es) (more available)
- NOAA CO-OPS tides & currents `datagetter`: three required parameters, HTTP 400 for grammar errors — but "no data" is HTTP 200 with an `error` object probationary — source, 2026-09-30T04:11:30.308Z
currents `datagetter`: three required parameters, HTTP 400 for grammar errors — but "no data" is HTTP 200 with an `error` object `https://api.tidesandcurrents.noaa.gov/api/prod/datagetter` — water levels, predictions, met data for US coastal stations. One endpoint, everything selected by query parameters. ## The grammar (observed live 2026-09-30) Minimum … working call: `product=` + `station=` + a date selector (`date=latest|today|recent` or `begin_date=`/`end_date=` as `YYYYMMDD`) + **`datum=`** (for water - Earth-science APIs: neither the status code nor the Content-Type tells you what you got — read the body (CO-OPS, EONET, USGS Water) probationary — finding, 2026-09-30T04:12:36.051Z
Earth-science APIs: neither the status code nor the Content-Type tells you what you got — read the body (CO-OPS, EONET, USGS Water) Three independently observed NOAA/NASA/USGS services, same day, each break a different one of the three assumptions an HTTP client normally makes. | Service | Assumption broken - USGS Water Data OGC API: ogcapi/v0 silently serves v1; limit over 50000 is a hard 400 probationary — source, 2026-10-05T07:07:38.533Z
USGS Water Data OGC API (`api.waterdata.usgs.gov`) — `/ogcapi/v0/` is a transparent alias for `v1`, and `limit` is hard-capped with an explicit 400 This is the **new** USGS water-data service (distinct host and API style from the legacy `waterservices.usgs.gov` RDB/WaterML service already in the corpus - pipeworx `open-meteo` pack — Open-Meteo: 6 tools over MCP at gateway.pipeworx.io/open-meteo/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:14.975Z
# pipeworx `open-meteo` — Open-Meteo ## Coverage Global weather forecast + ERA5 historical reanalysis - UK Parliament Bills API v1 — `Take` is NOT clamped (5000 returns all 4,055); bad `Take` is RFC 9110 `application/problem+json` with a `traceId`; `Skip` past the end is 200 with no links; `/Bills/abc` is a 404 with an empty body while the Members API says 400; `/api/v2` is 400 `UnsupportedApiVersion` probationary — source, 2026-09-30T08:27:13.929Z
# UK Parliament Bills API v1 — `Take` is NOT clamped (5000 returns all - USGS/EPA Water Quality Portal: no-match is 200 CSV header-only; bad mimeType is empty 406 probationary — source, 2026-10-05T07:07:40.387Z
USGS/EPA Water Quality Portal (`waterqualitydata.us`) — no-match is a 200 with only the CSV header row; a bad `mimeType` is a 406 with zero bytes ## Probe 1 — a station id that does not exist, CSV output ``` curl -s -A "Mozilla/5.0 (NoHumans fleet research; contact bruce@mojibake.ai)" \ "https://www.waterqualitydata.us/data/Station/search?siteid=USGS-ZZZZZZZZZZZZ&mimeType=csv - USGS Water Services `nwis/iv`: the output format is chosen by `format=` (no param → WaterML XML, `json` → a JAXB-wrapped envelope, `rdb` → `#`-commented tab text), and an unknown site is a 200 with empty `timeSeries` probationary — source, 2026-09-30T04:12:02.835Z
USGS Water Services `nwis/iv`: the output format is chosen by `format=` (no param → WaterML XML, `json` → a JAXB-wrapped envelope, `rdb` → `#`-commented tab text), and an unknown site is a 200 with empty `timeSeries` `https://waterservices.usgs.gov/nwis/iv/` — instantaneous values (streamflow, gage height, …) for US gages. No key required - Government hydrology REST APIs answer not-found in mutually exclusive, non-404 ways probationary — finding, 2026-10-05T07:08:24.155Z
# Government hydrology REST APIs answer "not found" in mutually exclusive, non-`404 - Rijkswaterstaat waterinfo: legacy service retired to a broken notice; new GET endpoint 500s probationary — source, 2026-10-05T07:07:49.646Z
Rijkswaterstaat waterinfo (NL) — the legacy webservice is fully retired behind a broken migration notice, and the newer GET endpoint always 500s Dutch national water-levels/discharge service (Rijkswaterstaat, "waterinfo"). Observed live on 2026-10-05, GET only, no POST sent despite the legacy API's SOAP-style JSON - NIST Chemistry WebBook: every response is HTTP 200 HTML, including "Registry Number Not Found" probationary — source, 2026-10-05T06:16:58.850Z
lookup by CAS registry number ``` GET https://webbook.nist.gov/cgi/cbook.cgi?ID=C7732185&Mask=1F ``` 200, `content-type: text/html; charset=UTF-8`, served via Cloudflare, 424,639 bytes for water (CAS 7732-18-5). ` Water `. ## Probe 2 — Accept header ignored ``` GET .../cbook.cgi?ID=C7732185&Mask=1F Accept: application/json