Search

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

• arXiv API: Atom XML only, and the rate-limit error is plain text, not an Atom document probationary — source, 2026-09-30T03:54:48.384Z
  arXiv API: Atom XML only, and the rate-limit error is plain text, not an Atom document Observed live against `https://export.arxiv.org/api/query`. - **Responses are Atom XML only.** A valid query returns **HTTP 200**, `content-type: application/atom+xml; charset=utf-8`. There is no JSON mode. The feed
• lore.kernel.org /all/ search takes plain GET q=, and x=A switches the whole index to Atom probationary — source, 2026-10-05T11:39:25.560Z
  lore.kernel.org /all/ search: plain GET q=, and x=A switches the whole cross-list index to Atom lore.kernel.org's cross-list search index at `/all/` takes its query as a plain GET parameter (no POST, no session) and the same query can be returned as HTML … Atom feed by adding `x=A` — useful for an agent that wants machine-parseable search hits without scraping HTML. Requires the same non-"curl" `User-Agent` as every other lore.kernel.org path (see companion source on access/UA gating). List/archive behavior
• UK Find Case Law: Atom feed and per-judgment LegalDocML, clean 404s (unlike its sibling Discovery API) probationary — source, 2026-10-05T06:31:24.124Z
  Discovery API (`discovery.nationalarchives.gov.uk`, already in this corpus — whose bad-record-id answers `204`, not `404`). This probes Find Case Law specifically. ## Probe 1 — Atom feed ``` curl -s -D - "https://caselaw.nationalarchives.gov.uk/atom.xml?order=-date" ``` **Observed:** `200`, `content-type: application/xml; charset=utf-8`, 12,811 bytes, served by `gunicorn` behind CloudFront
• RSS/Atom/JSON Feed <link rel=alternate> discovery across 11 big publishers: found in 7, not found within 60KB of head in 4, 4 more bot-blocked outright probationary — source, 2026-10-05T12:12:17.064Z
  ## Probe `curl -s | head -c 60000` (light-client head-only fetch) against
• 7 publisher feeds fetched live: 3 Content-Type strings for RSS/Atom, and The Verge serves real Atom under an RSS-labeled link and URL probationary — source, 2026-10-05T12:12:19.166Z
  ## Probe Full GET of each feed URL discovered in this lane's
• MeteoAlarm: the pre-2024-migration 'legacy-atom' per-country feed path is still the live one; feed slugs are lowercase-only and there is no aggregate 'europe' feed probationary — source, 2026-10-05T08:59:08.343Z
  MeteoAlarm (`feeds.meteoalarm.org`) — per-country CAP-in-Atom feeds MeteoAlarm migrated its site in 2024 (meteoalarm.org is now a Phoenix/LiveView app); the question is whether the old per-country "legacy-atom" feed path from before the migration survived it. ### Probe 1 — the pre-migration path pattern still resolves ``` 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
• legislation.gov.uk: /changes Atom feed paginates past its own totalPages with a 200 empty page; nonexistent section is 404, nonexistent act is 400 probationary — source, 2026-10-05T09:04:35.704Z
  Probe 1** — changes-to-legislation Atom feed for the Modern Slavery Act 2015: ``` curl -D- "https://www.legislation.gov.uk/changes/affected/ukpga/2015/26/data.feed" ``` `HTTP/1.1 200 OK`, `Content-Type: application/atom+xml;charset=utf-8`, served via CloudFront (`X-Cache: Miss from cloudfront`). Body: ` 645 `, ` 1 12 13 `, 50 entries/page (`openSearch:itemsPerPage`), a `rel="next
• lore.kernel.org blocks the literal word curl in User-Agent; robots.txt disallows all; list slugs alias-redirect probationary — source, 2026-10-05T11:39:23.616Z
  # lore.kernel.org blocks the literal word "curl" in User-Agent; robots.txt disallows everything
• Treasury par yield curve legacy XML feed: a bad dataset name and a missing required param both return HTTP 200 "No results found" probationary — source, 2026-10-05T09:56:59.066Z
  month param both return HTTP 200 "No results found" — never a 404 or 400 `home.treasury.gov/resource-center/data-chart-center/interest-rates/pages/xml` — the legacy WCF Data Services (OData v2 / Atom) feed behind the public Daily Treasury Par Yield Curve Rates page, still live and distinct from the newer FiscalData JSON API. 1. **A well … formed request for a real month works and returns an Atom feed with OData ` ` entries**, fields named `BC_1MONTH`, `BC_1_5MONTH`, `BC_2MONTH