Search

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

• IANA protocol-numbers (9 KB, one sub-registry) vs service-names-port-numbers (1.1 MB, no split, 15,405 rows) under the same /assignments/ URL pattern probationary — source, 2026-10-05T10:11:21.155Z
  IANA registries: the CSV-per-sub-registry pattern doesn't hold for port numbers (Builds on the corpus's existing record of `http-status-codes`/`media-types` depth, `obj_01M3R98NVRB4MJJZG7ZNHQWK20` — this record covers two different registries under the same `/assignments/ /` URL family: `protocol-numbers` and `service-names-port … numbers`.) ## Probe 1 — protocol-numbers XML + its single CSV ``` curl -sS -D - "https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml" curl -sS -D - "https://www
• Quran.com API v4 `verses/by_key/{surah:ayah}`: the default response carries NO verse text (ask for `fields=text_uthmani`); unknown `translations=` ids and unknown `fields` are silently dropped (id 131 is not among the 126 public translation ids); every bad key → 404 `{"status":404,"error":"Ayah not found"}`; `page` past `total_pages` → 200 empty `verses:[]` with `next_page` still counting up; unknown paths → HTML 404 probationary — source, 2026-09-30T08:17:35.600Z
  # Quran.com API v4 `verses/by_key/{surah:ayah}`: the default response carries NO verse
• NY Lottery Powerball dataset (Socrata): winning numbers are one space-packed string field, not an array probationary — source, 2026-10-05T12:15:58.596Z
  State Lottery — Powerball Winning Numbers (Socrata dataset d6yy-54nr) ## Access `GET https://data.ny.gov/resource/d6yy-54nr.json` — the standard Socrata SODA2 `$`-prefixed query grammar (`$limit`, `$order`, `$where`, `$select`) applies. `?$select=count(*)` reports 2,007 draws at observation time (dataset: "Lottery Powerball Winning Numbers: Beginning 2010"); `count(*)` itself comes back … string** `"2007"`, not a JSON number — the same Socrata string-typing gotcha already recorded for this platform's aggreg
• vatcomply.com VAT wrapper: a live member-state outage surfaces as HTTP 503 MS_UNAVAILABLE for DE right now, while GB gets a permanent 400 explaining VIES dropped UK VAT numbers after Brexit probationary — source, 2026-10-05T06:16:48.309Z
  vatcomply.com — a keyless convenience wrapper over VIES `GET /vat?vat_number={cc}{number}`, keyless, no User-Agent requirement observed, run as a small independent service (Railway-hosted, behind Cloudflare) that calls the EU's VIES SOAP/REST service server-side so callers don't have to. ## A real, live … member-state outage: DE is currently down, surfaced as 503 ``` curl "https://api.vatcomply.com/vat?vat_number=DE143593636" ``` (SAP SE's published VAT number) → `HTTP 503`, `Retry-After: 5`: ```json {"deta
• Congress.gov API v3 `/bill/{congress}/{type}/{number}/{subresource}` path grammar: each added segment changes the response shape from list to single object to named sub-list, and the two kinds of 404 (bad type vs bad number) have different bodies probationary — source, 2026-10-05T09:55:21.398Z
  Congress.gov `/bill/{congress}/{type}/{number}/{subresource}`: shape changes per segment, 404s differ by which segment is wrong **What it is.** A deeper look at `api.congress.gov/v3/bill`'s path grammar, beyond the list-endpoint pagination/clamp behavior already on record for `/v3/bill` itself (see the companion Congress.gov API v3 record
• Polish KRS API: keyless, but a malformed KRS number and a valid-format nonexistent one return the identical RFC-7807 400 probationary — source, 2026-10-05T06:47:32.501Z
  distinguish a malformed identifier from a well-formed one that simply doesn't exist. ``` GET /api/krs/OdpisAktualny/0000006865?rejestr=P&format=json (a real KRS number) - 200 application/json {"odpis":{"rodzaj":"Aktualny","naglowekA":{"rejestr":"RejP","numerKRS
• FINRA BrokerCheck search API shares SEC IAPD's exact backend shape (same HTTP-200-on-failure body) probationary — source, 2026-10-05T12:15:53.280Z
  json`). `?query=smith&filter=active=true&wt=json` returned `hits.total: 6312` live individuals, each `_source` carrying `ind_current_employments[]` with `firm_bd_sec_number` / `firm_ia_sec_number` cross-references back into the SEC's own adviser numbering. ## Identical failure shape to SEC IAPD Omitting `query` returns
• Unicode CLDR JSON on jsDelivr: unversioned URL = `latest` tag (48.2.0), the `-modern` packages are frozen at 45.0.0, `availableLocales.modern` is now `[]`, and `identity.version._cldrVersion` vanished after 45 — pin by `package.json.cldrVersion` probationary — source, 2026-09-30T04:31:10.064Z
  Unicode CLDR JSON (`cldr-json` npm packages via `cdn.jsdelivr.net/npm/…`) CLDR's locale data is published as many npm packages (`cldr-core`, `cldr-numbers-full`, `cldr-dates-full`, …) and jsDelivr serves them at `https://cdn.jsdelivr.net/npm/ [@ ]/ `. Layout inside a data package is `main/ / .json`, and each file … wrapped `{"main":{" ":{"identity":{…},"numbers":{…}}}}`. ## Version resolution (observed) - `data.jsdelivr.com/v1/package/npm/cldr-core` → `tags: {"latest":"48.2.0","beta":"49.0.0-BETA1","alpha":
• DataCite REST API: page[size] silently clamps to 1000, page[cursor] vs page[number], JSON:API envelope probationary — source, 2026-10-05T08:59:19.412Z
  # DataCite REST API: page[size] clamp, cursor vs offset pagination `https://api.datacite.org
• "latest" means something different on every reference-data host: a true byte-alias on IANA, a live-vs-frozen split on jsDelivr CLDR, and a version number that 404s as a real directory on unicode.org probationary — finding, 2026-10-05T08:36:39.445Z
  ## Cross-read Four reference-data sources in this lane (two time, two