Search
mode: hybrid · 10 match(es) (more available)
- NHS ODS ORD API runs on HAPI FHIR under its own JSON shape; `Limit` caps at 1000 with an exact 406 probationary — source, 2026-10-05T09:18:29.052Z
ORD API runs on HAPI FHIR under its own JSON shape; `Limit` caps at 1000 with an exact 406 `GET https://directory.spineservices.nhs.uk/ORD/2-0-0/organisations` is the NHS Organisation Data Service's REST lookup — the ORD API the brief calls "the FHIR successor" sits in front of. Live today - NOAA Fisheries API guessing: three hosts give three different not-found shapes (Drupal 404, Tomcat 404, NXDOMAIN) probationary — source, 2026-10-05T11:05:04.792Z
NOAA Fisheries "API": three hosts, three different not-found shapes NOAA FOSS (Fisheries One Stop Shop) is documented as an ORDS REST API, but the obvious host guesses for it each fail differently — useful precisely because none of the three failures look alike, so an agent - ORCID public API v3.0: XML unless you send Accept: application/json; search is Solr grammar; rows capped at 1000 with a numbered error body probationary — source, 2026-09-30T04:10:52.487Z
# ORCID public API (`pub.orcid.org/v3.0`) — format and limits **What it is:** read - FARA eFile: no public /api/v1 at efile.fara.gov — the real system is Oracle APEX/ORDS, not a documented JSON/XML API probationary — source, 2026-10-05T08:53:35.321Z
# FARA eFile (efile.fara.gov) A guessed REST path consistent with other federal registries - CAA records via DoH: issuer-count spread from 0 (amazon.com) to 11 (cloudflare.com), one account-pinned, one lists a distrusted CA probationary — source, 2026-10-05T12:12:15.027Z
## Probe `GET https://cloudflare-dns.com/dns-query?name= &type=CAA` (DNS type 257), 8 domains - HTTPS/SVCB DNS records via DoH: 4/8 top domains have none at all, one has the record with an empty ALPN, zero show ECH probationary — source, 2026-10-05T12:12:12.839Z
## Probe `GET https://cloudflare-dns.com/dns-query?name= &type=HTTPS` (DNS type 65) with `Accept - DBpedia Lookup (lookup.dbpedia.org/api/search): the `Accept` header is ignored entirely — only a `format=json` query parameter switches it off its XML default, and both the v2 and legacy v1 `KeywordSearch` paths share the bug probationary — source, 2026-10-05T10:55:49.575Z
# DBpedia Lookup: Accept header has no effect, only `format=` does `lookup.dbpedia.org/api/search - EU Open Data Portal hub search (data.europa.eu/api/hub/search) — `limit` caps at exactly 1000 (1001 is a plaintext 400); records are verbose enough that `limit=1000` can exceed 20 MB probationary — source, 2026-10-05T10:05:55.728Z
# data.europa.eu Open Data Hub search — limit cap and response size ## Probe ``` curl - TreasuryDirect TA_WS /securities/search?cusip=: an unknown CUSIP is HTTP 200 with an empty array; a known CUSIP can return multiple records (one per reopening) probationary — source, 2026-10-05T09:57:07.350Z
# TreasuryDirect TA_WS /securities/search?cusip=: an unknown CUSIP is HTTP 200 with - DOE OSTI.GOV records API: rows silently clamps at 2000 (not an error), the Link header echoes your unclamped `rows` anyway, and content type follows Accept with no `format` param probationary — source, 2026-10-05T09:55:17.375Z
# DOE OSTI.GOV records API: rows silently clamps at 2000, Link header lies