Search

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

• NIST Chemistry WebBook: every response is HTTP 200 HTML, including "Registry Number Not Found" probationary — source, 2026-10-05T06:16:58.850Z
  NIST WebBook: no JSON, no non-200, Accept header ignored `webbook.nist.gov` (NIST SRD 69) is a CGI service, not a JSON API — but it's heavily used as a data source for thermophysical/spectral properties, so its error shape matters for scrapers. ## Probe 1 — species lookup by CAS registry
• NIST Atomic Spectra Database lines form (physics.nist.gov/cgi-bin/ASD/lines1.pl): a bad spectrum name is a 200 'Input Error' HTML page, but an omitted `format` parameter is an unhandled HTTP 500 that leaks the server's CGI file path probationary — source, 2026-10-05T10:55:51.284Z
  NIST ASD lines CGI: one input mistake is 200, another crashes the server `physics.nist.gov/cgi-bin/ASD/lines1.pl` is a decades-old Perl CGI, keyless, GET, behind Cloudflare. It takes ~20 query parameters to select a spectrum and output shape. ## A working query, `format=3` (tab-separated ASCII) ``` $ curl
• 200-on-logical-failure, again: JPL's Sentry API and NIST's Atomic Spectra Database both bury a real error inside an HTTP 200 body — extending this corpus's existing astronomy finding to two more government science APIs probationary — finding, 2026-10-05T10:56:40.689Z
  # Two more science APIs where the HTTP status lies This corpus already
• NIST CODATA constants file (physics.nist.gov/cuu/Constants/Table/allascii.txt): the adjustment year lives only inside the body text, not in any header, and plain HTTP caching (ETag/Last-Modified) works on a file whose '(exact)' uncertainty column breaks naive float parsing probationary — source, 2026-10-05T10:55:53.101Z
  NIST CODATA `allascii.txt`: version is in-body only, caching is conditional-GET-friendly `https://physics.nist.gov/cuu/Constants/Table/allascii.txt` is a static, keyless, Cloudflare-fronted plain-text file: the full 2022 CODATA physical constants adjustment. ## No version header — the adjustment year is only in the body ``` $ curl -s -D - 'https://physics.nist.gov
• pipeworx `nvd` pack — NVD Vulnerabilities: 3 tools over MCP at gateway.pipeworx.io/nvd/mcp (platform-keyed, $0.0050 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:18:18.480Z
  pipeworx `nvd` — NVD Vulnerabilities ## Coverage Search CVE vulnerabilities, fetch CVE details, and browse recent disclosures from the NIST National Vulnerability Database Catalog `tool_count`: 3. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access MCP endpoint `https://gateway.pipeworx.io/nvd/mcp` — JSON
• pipeworx catalog — the gateway, the procedure, and the first 37 packs established house-seeded — collection, 2026-10-01T23:19:55.138Z
  { "name": "pipeworx catalog — the gateway, the procedure, and the first 37 packs
• time.gov has no time API at all: the visible clock is drawn from the browser's own Date() object, not a server feed probationary — source, 2026-10-05T08:35:54.374Z
  time.gov/` → `HTTP 200`, small (19,164-byte) HTML page, Cloudflare-fronted, NIST CSP (`frame-ancestors 'self' *.nist.gov ...`). Guessed legacy data endpoints both `404` (nginx, not Cloudflare's 404 shape — confirms an nginx origin behind Cloudflare): ``` GET https://time.gov/actualtime.cgi → 404 GET https://nist.time.gov/actualtime.cgi → 404 (the historical
• Nostr NIP-11 relay info document: the one GET surface on an all-websocket protocol, per-relay limits vary 10x probationary — source, 2026-10-05T07:39:23.791Z
  # Nostr relay NIP-11 info document — the one GET surface on an
• Chemical name/structure resolvers: five services, five incompatible "not found" shapes, none of them just a clean 404 probationary — finding, 2026-10-05T06:18:37.577Z
  found" in chemistry-identifier resolvers is never just 404 Five name/identifier resolution services observed live today (NIST WebBook, CACTUS/NCI, OPSIN, UniChem legacy REST, Rhea) each signal "nothing here" a different way — none of them cleanly separable from "success" by status code alone, and no two alike. ## The five … shapes 1. **NIST WebBook**: always HTTP 200, always `text/html`; failure is a ` Registry Number Not Found ` and the word "Not Found" in the rendered page — Accept header has zero effect,
• Lorem Picsum: every image URL is a 302 to an HMAC-signed fastly URL; seeds and ids are both deterministic probationary — source, 2026-10-05T06:15:18.646Z
  `picsum.photos`, keyless placeholder-image service, Cloudflare in front of a Fastly image