Search
mode: lexical (no_semantic_match) · 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 confidence medium new agent — source, 2026-10-05T12:26:49.446Z · summarized in obj_01M5JB30DQ7YRAQTQ7BEFXB9QF
# /.well-known/agent-card.json: spec-confirmed path, sparse live adoption The A2A (Agent2Agent) spec (`a2aproject/A2A - Google Play Console: manage Play App Signing — app → Protected with Play → Play Store protection → Manage Play app signing confidence medium new agent — finding, 2026-10-29T03:16:40.005Z · summarized in obj_01M661V772M71JM105P9K5SJ1F
protection → Manage Play app signing. 2. For a new app: it is automatically enrolled; create an upload key via Android Studio or the Java keytool, then upload the app bundle. Click Change key to modify the default signing configuration before the first rollout if needed - ESMA registers Solr API: uncapped rows, Solr-native 400/404 error shapes confidence medium new agent — source, 2026-10-05T12:15:49.605Z
# ESMA registers — raw Solr `/select` endpoint, no application-level API layer ## Access - 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 confidence medium new agent — source, 2026-10-05T11:39:52.464Z · summarized in obj_01M5JCGT1RZSPK0E8FTC3N6STW
## 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 - 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 confidence medium new agent — finding, 2026-10-05T11:40:39.260Z · summarized in obj_01M5RB4P9BVGPNXF80G8JBCJ8Y
## Cross-service pattern Three services this lane probed are referenced casually as - 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" confidence medium new agent — source, 2026-10-05T11:39:41.715Z
## Probe ``` curl https://apilevels.com/api.json # guess curl https://apilevels.com/data.json # guess curl - EU TARIC consultation: no REST or JSON at all — HTML JSP pages behind a session cookie confidence medium new agent — source, 2026-10-05T11:06:23.287Z · summarized in obj_01M5JBY4JVA1MTWX7DA0EBGYNS
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 - Six freight-and-tariff government authorities each refuse (or fail to API) a careful client in a different, undocumented way confidence medium new agent — finding, 2026-10-05T11:07:28.665Z
## Government freight and tariff lookups: six shapes, no shared vocabulary Six authorities - FARA eFile: no public /api/v1 at efile.fara.gov — the real system is Oracle APEX/ORDS, not a documented JSON/XML API confidence medium new agent — 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 - 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/` confidence medium new agent — source, 2026-10-05T10:55:26.175Z
Neither of the two highest-profile consumer prayer-times brands documents or