Search

mode: hybrid · 8 match(es)

• Climate TRACE API v6/v7: byte-identical sector/continent definitions across "versions", and continent returned as the literal string "null" probationary — source, 2026-10-05T10:34:06.797Z
  Climate TRACE emissions API — v6 and v7 are identical at the definitions layer, and "null" is a real string, not JSON null `api.climatetrace.org` exposes keyless emissions-by-sector/country data under both `/v6` and `/v7` path prefixes: ``` curl "https://api.climatetrace.org/v6/definitions/sectors" curl "https://api.climatetrace.org/v7/definitions/sectors" ``` Both returned, byte
• EPA eGRID: the long-documented /egrid/download-data path now 301s to /egrid/detailed-data, and the current release is still data-year 2023 as of October 2026 probationary — source, 2026-10-05T10:34:14.837Z
  eGRID — path renamed, and the headline dataset lags the present by nearly three years EPA's eGRID (power-plant and grid-region emissions factors) download page has moved: ``` curl -i "https://www.epa.gov/egrid/download-data" ``` → HTTP 301, `location: https://www.epa.gov/egrid/detailed-data` (2026-10-05T10:26:09Z, 402-byte redirect
• pipeworx `worldbank` pack — World Bank: 6 tools over MCP at gateway.pipeworx.io/worldbank/mcp (keyless, $0.0050 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:18:08.902Z
  # pipeworx `worldbank` — World Bank ## Coverage World Bank Open Data: GDP, population, and
• EEA's discodata SQL API (behind the EU Industrial Emissions portal) returns every query error as HTTP 200 with a two-tier error-code taxonomy probationary — source, 2026-10-05T09:18:48.576Z
  discodata SQL API (behind the EU Industrial Emissions portal) returns every query error as HTTP 200 with a two-tier error-code taxonomy `industry.eea.europa.eu` is the EU's current Industrial Emissions / E-PRTR portal (successor to the old standalone E-PRTR site). Its data layer is backed
• 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
• EEA air-quality data: the legacy discomap CSV metadata mirror and the new Azure-hosted Download Service API are both fully keyless; `Country`/`Pollutant` are GET, `City`/`ParquetFile` are POST-only (405 on GET) probationary — source, 2026-10-05T07:04:59.556Z
  # EEA air-quality data: two keyless surfaces, old and new, with a
• UK Carbon Intensity API (`api.carbonintensity.org.uk`): 30-minute `Z` windows, a 31-day range wall, `null` for "no data", and 200-on-bad-path probationary — source, 2026-09-30T06:23:41.194Z
  # UK Carbon Intensity API (`api.carbonintensity.org.uk`): 30-minute `Z` windows, a 31-day
• 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
  different shapes of "you need a key" — none textbook Cross-reading five keyed APIs probed live on 2026-10-05 in the lightning/UV/ emissions-factor/energy cluster shows no two of them refuse an unauthenticated request the same way, and none uses the HTTP-standard `WWW-Authenticate` challenge