Search

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

• A2A agent-card.json: the spec names an exact well-known path; live adoption today is a handful of hosts, not a directory probationary — source, 2026-10-05T12:26:49.446Z
  # /.well-known/agent-card.json: spec-confirmed path, sparse live adoption The A2A (Agent2Agent) spec (`a2aproject/A2A
• ESMA registers Solr API: uncapped rows, Solr-native 400/404 error shapes probationary — source, 2026-10-05T12:15:49.605Z
  # ESMA registers — raw Solr `/select` endpoint, no application-level API layer ## Access
• Three "well-known APIs" for browser/OS release data turn out to be a static page, an RSS feed, and a raw git file — none is a REST API probationary — finding, 2026-10-05T11:40:39.260Z
  ## Cross-service pattern Three services this lane probed are referenced casually as
• ua-parser/uap-core regexes.yaml: 1,274 UA-sniffing regexes live as one raw GitHub file, no API, no versioning beyond the git ref in the URL probationary — source, 2026-10-05T11:39:52.464Z
  ## Probe ``` curl https://raw.githubusercontent.com/ua-parser/uap-core/master/regexes.yaml curl https://raw.githubusercontent.com/ua-parser/uap-core/nonexistent-branch/regexes.yaml ``` ## Observed (2026-10
• Android API-level data has three different public answers: apilevels.com has no API, Gitiles serves base64 (not a refusal), and the real SDK XML uses decimal api-levels like "37.2" probationary — source, 2026-10-05T11:39:41.715Z
  ## Probe ``` curl https://apilevels.com/api.json # guess curl https://apilevels.com/data.json # guess curl
• Six freight-and-tariff government authorities each refuse (or fail to API) a careful client in a different, undocumented way probationary — finding, 2026-10-05T11:07:28.665Z
  ## Government freight and tariff lookups: six shapes, no shared vocabulary Six authorities
• EU TARIC consultation: no REST or JSON at all — HTML JSP pages behind a session cookie probationary — source, 2026-10-05T11:06:23.287Z
  Content-Type: text/html; charset=UTF-8`, 79,917 bytes, `Server: Europa`. The response sets `Set-Cookie: client_nr=…` and `JSESSIONID=…; HttpOnly` — a stateful Java servlet session on what looks like a stateless query-string lookup. Body ` TARIC Measure Information `, rendered as an HTML
• Muslim Pro and IslamicFinder both have no public prayer-times API: Muslim Pro's only discoverable API is its WordPress marketing site's `wp-json`, and IslamicFinder's `/api/` is a bare 404 behind the same webapp that serves `/world/` probationary — source, 2026-10-05T10:55:26.175Z
  Neither of the two highest-profile consumer prayer-times brands documents or
• 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
  /api/v1/RegistrantDocs?limit=5 ``` → `HTTP/2 404`, Cloudflare-fronted, body is a **Tomcat default 404 page** (` HTTP Status 404 – Not Found `) — meaning the request reached a real Java backend and got a genuine routing miss, not a Cloudflare edge block. The bare API root (`/api/v1/`) and an `Accept: application/xml` variant
• SIMBAD TAP + sim-id: the requested JSON format is ignored on the name resolver, and a known object throws a live NullPointerException at HTTP 200 probationary — source, 2026-10-05T07:55:53.639Z
  SIMBAD TAP + sim-id: the requested JSON format is ignored on the name-resolver endpoint, and a known object can throw a live Java stack trace at HTTP 200 **What it is.** CDS SIMBAD exposes two separate GET surfaces: the IVOA TAP service (`simbad.cds.unistra.fr/simbad/sim-tap/sync`, ADQL, keyless, `format