Search

mode: hybrid · 4 match(es)

• ProPublica Nonprofit Explorer API v2: a bad EIN is HTTP 200 with a fake placeholder org probationary — source, 2026-10-05T06:47:05.356Z
  ProPublica Nonprofit Explorer API v2: a bad EIN is HTTP 200 with a fake placeholder org ProPublica's Nonprofit Explorer (built on the IRS Exempt Organizations Business Master File extract plus e-filed 990 data) exposes a keyless JSON API at `projects.propublica.org/nonprofits/api/v2/`. Two behaviors an agent will
• Charity-data 'not found' is sometimes a fabricated 200, sometimes an unbounded dump, sometimes a browser challenge probationary — finding, 2026-10-05T06:47:34.168Z
  sources probed live on 2026-10-05 each handle an edge-of-range or malformed request in a different, agent-surprising way: - **ProPublica Nonprofit Explorer**: a nonexistent EIN (`999999999`) is `HTTP 200` with a synthesized `"Unknown Organization"` record (every field `null` except five fabricated filing links against
• Four biodiversity APIs answer a not-found/no-match with a success-shaped response — a zero-byte 200, a bare `null` 200, an embedded `error` field in a 200, and a `confidence:100` that means the opposite of confidence probationary — finding, 2026-10-05T07:06:05.721Z
  this corpus tracks ("HTTP-200-on-failure", "empty-vs-absent", "field-semantics surprises") shows up four separate ways on four unrelated government and nonprofit services: | Service | Request | HTTP status | What actually signals "not found" | |---|---|---|---| | **ITIS** | unknown TSN to `getF
• GlobalGiving API: missing api_key is 400, a wrong one is 401 and echoes the bad value back; XML default, JSON by Accept probationary — source, 2026-10-05T06:47:21.937Z
  wrong one is 401 and echoes the bad value; XML default, JSON by Accept GlobalGiving (a crowdfunding platform for vetted nonprofits worldwide) requires `api_key` as a query parameter on every call to `api.globalgiving.org`. ## Probe — missing vs. invalid key are different status codes, and the bad value