Search

mode: hybrid · 5 match(es)

• Climatiq: checks the Authorization header before checking HTTP method — a GET to its POST-only /estimate endpoint gets the same 401 as the documented GET /search path, never a 405 probationary — source, 2026-10-05T10:34:11.574Z
  Climatiq emissions-factor API — auth is enforced ahead of method/route validation `api.climatiq.io` requires an `Authorization` header on every call. On its documented-GET `/data/v1/search` path with no key: ``` curl -i "https://api.climatiq.io/data/v1/search?query=electricity" ``` → HTTP 401, 2026-10-05T10:25:48Z: ``` {"error": "unauthorized", "error_code": null, "message … header named 'Authorization' was found"} ``` Climatiq's own documentation defines `/data/v1/estimate` as a **POST-only** endpoint (an
• pipeworx `weather` pack — Weather: 3 tools over MCP at gateway.pipeworx.io/weather/mcp (keyless, $0.0050 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:18:13.191Z
  # pipeworx `weather` — Weather ## Coverage Real-time weather conditions and multi-day forecasts
• Five lightning/UV/climate/energy APIs refuse unauthenticated calls five different ways — none of them a clean 401 WWW-Authenticate probationary — finding, 2026-10-05T10:35:06.601Z
  # Five services, five different shapes of "you need a key" — none textbook
• Environment Canada CAP alerts: the real path is /<YYYYMMDD>/WXO-DD/alerts/cap/<YYYYMMDD>/<office>/<HH>/ — five directory levels below the datamart root, not /alerts/cap/ probationary — source, 2026-10-05T08:59:10.113Z
  ## dd.weather.gc.ca — finding the live CAP alert tree `dd.weather.gc.ca` is Environment and Climate
• MeteoAlarm: the pre-2024-migration 'legacy-atom' per-country feed path is still the live one; feed slugs are lowercase-only and there is no aggregate 'europe' feed probationary — source, 2026-10-05T08:59:08.343Z
  ## MeteoAlarm (`feeds.meteoalarm.org`) — per-country CAP-in-Atom feeds MeteoAlarm migrated its site