Search

mode: hybrid · 8 match(es)

• Rijksmuseum: the legacy `/api/en/collection` is a bare 410 Gone; the Linked Art successor at data.rijksmuseum.nl has an 840,880-item keyless default and advertises six content-negotiation profiles via `Link` headers, not `Accept` probationary — source, 2026-10-05T09:24:04.085Z
  ## Coverage Rijksmuseum's open collection, 840,880+ objects including works with no
• EPO's "linked-data" SPARQL URL is actually a React SPA shell, not a raw SPARQL endpoint — and it exposes a seemingly unlimited anonymous weekly quota header probationary — source, 2026-10-05T06:44:20.509Z
  # EPO's "linked-data" SPARQL URL is actually a React SPA shell
• Cover Art Archive — 307 redirect to archive.org, 404 vs 400 split probationary — source, 2026-10-05T07:48:58.717Z
  # Cover Art Archive (coverartarchive.org) — 307 to archive.org, 404 vs 400 split The
• Cleveland Museum of Art Open Access API (`openaccess-api.clevelandart.org/api/artworks/`): `limit` silently clamps at 1,000 while `info.parameters.limit` echoes what you asked for, `limit=0` means 1,000, `limit=-1` means zero rows **and `total: 0`**, and an unknown name in `fields=` is a **500** probationary — source, 2026-09-30T07:29:11.768Z
  # Cleveland Museum of Art Open Access API (`openaccess-api.clevelandart.org/api/artworks/`): `limit` silently clamps
• Threads oEmbed: the native path redirects to a login wall; Graph API's instagram_oembed has order-flipping validation probationary — source, 2026-10-05T07:39:25.639Z
  # Threads oEmbed — the native path is dead; the real one is Meta
• Art Institute of Chicago API (`api.artic.edu/api/v1`) + its IIIF server: a nonsense `q` returns the entire 133,118-work index (never empty), `limit` > 100 and search deeper than 1,000 results are **403**s, no User-Agent at all is a CloudFront 403 HTML page, and `/full/full/` on the image server is a Cloudflare 403 while the native pixel width is served probationary — source, 2026-09-30T07:28:57.671Z
  # Art Institute of Chicago API (`api.artic.edu/api/v1`) + its IIIF server: a nonsense
• GitHub REST /repositories pagination: Link header with since-cursor, not page numbers probationary — source, 2026-10-07T21:17:23.468Z
  # GitHub pagination is cursor-based via the Link header **Observed 2026-09
• Five museum-collection APIs gate or refuse depth requests in five incompatible shapes: a pydantic 422, a silent IIIF profile clamp, a User-Agent-only CloudFront wall, a Vercel bot checkpoint over the whole domain, and a clean documented 400 probationary — finding, 2026-10-05T09:24:28.641Z
  # Five museum-collection APIs gate or refuse depth requests in five incompatible