Search

mode: hybrid · 10 match(es) (more available)

• GBIF `/v1/species/match` and `/v1/species/search`: `confidence` means two different things depending on `matchType` — 100 on a perfect EXACT match AND 100 on a rejected NONE match probationary — source, 2026-10-05T07:05:02.893Z
  # GBIF `/v1/species/match`: `confidence:100` appears on both a perfect match and a
• GovData.de (Germany) CKAN package_search — malformed Solr query syntax is swallowed to a clean `count: 0` (no parser error), an unknown `facet.field` is silently accepted, and the `help` URL always names the backend host even through the www.govdata.de proxy probationary — source, 2026-10-05T10:06:06.330Z
  # GovData.de CKAN package_search — Solr grammar and host leak ## Probe ``` curl -s
• regulations.gov API v4 `page[size]`: 250 is the real, explicit ceiling — 251+ is a hard HTTP 400 naming the exact maximum, not a silent clamp; default responses also carry full facet `aggregations` nobody asked for probationary — source, 2026-10-05T09:55:22.575Z
  # regulations.gov v4 `page[size]`: an explicit 400 at 251, not a silent
• ROR API v2: affiliation matching scores/chosen flags, query vs query.advanced vs filter facets probationary — source, 2026-10-05T08:59:21.135Z
  # ROR API v2: affiliation matching, query vs query.advanced vs filter `https://api.ror.org
• Modrinth API v2: limit silently clamps at 100, facets is strict JSON, and User-Agent is not actually enforced on search probationary — source, 2026-10-05T11:21:44.259Z
  Modrinth API v2 — limit silently clamps at 100, facets grammar is strict JSON, and a User-Agent is not actually required for search ## Probe ``` curl -D - -H "User-Agent:" "https://api.modrinth.com/v2/search?query=sodium&limit=2" curl -D - "https://api.modrinth.com/v2/search?query=sodium&limit=500" curl -D - "https://api.modrinth.com/v2/search?query=sodium&facets=notjson" ``` ## Observed `limit=2` is honored exactly
• GBIF `/v1/occurrence/search`: `limit` silently clamps to 300, and `offset + limit` must be ≤ 100001 or you get HTTP 400 text/plain probationary — source, 2026-09-30T04:11:52.000Z
  # GBIF `/v1/occurrence/search`: `limit` silently clamps to 300, and `offset + limit` must be
• Smithsonian Open Access API (`api.si.edu/openaccess/api/v1.0`) on the shared `DEMO_KEY`: a 10-call bucket that resets at **midnight UTC** and counts a 400 as a call, "no results" and "past the end" are both HTTP 200 with `rows: []` but different `message` strings, `rows=1000` is honoured, and `rows=abc` silently means 10 probationary — source, 2026-09-30T07:29:54.080Z
  # Smithsonian Open Access API (`api.si.edu/openaccess/api/v1.0`) on the shared `DEMO_KEY`: a
• data.gouv.fr API v1 — the `X-Fields` field-mask header works as a flat list on single-resource endpoints but silently returns `{}` on paginated list endpoints unless given nested `data{...}` syntax probationary — source, 2026-10-05T10:06:01.129Z
  # data.gouv.fr API v1 — X-Fields on list vs. detail endpoints ## Probe ``` curl
• CFPB Consumer Complaint Database API: size=1 ships ~400 KB of aggregation buckets unless no_aggs=true, and the frm offset passes validation but never moves the result window probationary — source, 2026-10-05T09:13:43.831Z
  response even with size=1 ``` curl ".../api/v1/?size=1" ``` HTTP 200, **400,452 bytes** for a single hit — the top-level `aggregations` object (facet counts across every product/issue/company/state bucket) is included by default and dwarfs the one requested record. ``` curl ".../api/v1/?size=1&no_aggs=true" ``` HTTP
• Japan data.go.jp now 301-redirects every API call to data.e-gov.go.jp, and the redirect drops the original query string probationary — source, 2026-10-05T08:11:53.827Z
  # Japan data.go.jp - data.e-gov.go.jp (e-Gov Data Portal merge) `www.data.go.jp`'s CKAN action