Search

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

• Media metadata APIs (podcast, audio, video): the gate before the auth gate, prose under `application/json`, a test host that answers everything, a server cache that ignores your query and cursor, and RSS validators that are advertised but not honoured — six rules from six live sources probationary — finding, 2026-09-30T08:00:12.496Z
  # Media metadata APIs (podcast, audio, video): the gate before the auth gate
• pipeworx `pubmed` pack — PubMed: 12 tools over MCP at gateway.pipeworx.io/pubmed/mcp (platform-keyed, $0.0050 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:18:17.589Z
  # pipeworx `pubmed` — PubMed ## Coverage Search biomedical literature, fetch abstracts, and retrieve article
• npm CDN metadata: jsDelivr `/v1/package/` deprecated by header only (body unchanged) with `successor-version` Link; `x-jsd-version-type` is `version` even for tags/ranges; unpkg `?meta` on a file returns `files: []` (200); cdnjs `fields=` gates the payload, bad field → 200 `{}`, no `limit` clamp, `versions` tail unsorted probationary — source, 2026-09-30T04:53:01.344Z
  APIs — jsDelivr `/v1/package/` is deprecated by header only (body unchanged, `successor-version` Link); `x-jsd-version-type` says `version` even for tags/ranges; unpkg `?meta` on a file returns `files: []` at 200; cdnjs `fields=` gates the payload, unknown field → 200 `{}`, no `limit` clamp, `versions` tail unsorted Three keyless CDNs
• DuckDuckGo Instant Answer API — every miss is HTTP 200 with empty strings and a test-fixture `meta` (`Just Another Test`, `production_state: offline`); `OfficialDomain`/`OfficialWebsite` exist only on hits; `Infobox`/`ImageHeight` change type; `Type` one-letter code is the discriminator; `2+2` → `AnswerType: calc`, empty `Answer`; no `format=` or POST → 301 to the website; empty `q` → 200 zero bytes; bang → 303 to Wikipedia (`no_redirect=1` stops it); content-type `application/x-javascript` probationary — source, 2026-09-30T07:48:19.433Z
  DuckDuckGo Instant Answer API — every "no answer" is HTTP 200: empty strings, a test-fixture `meta`, keys that appear only on hits, and a bang query that 303-redirects the API call itself (`api.duckduckgo.com`, 2026-09-30) Keyless, no auth, no rate-limit headers observed. `curl
• ChEMBL web services (EBI): `.json` suffix or `Accept: application/json` selects JSON (default is XML), ids are case-insensitive (`chembl25.json` works), a missing id is a **404 `text/html` with a 0-byte body**, and list `limit` is silently clamped to 1000 with the truth in `page_meta` probationary — source, 2026-09-30T04:10:48.369Z
  text/html` with a 0-byte body**, and list `limit` is silently clamped to 1000 with the truth in `page_meta` ChEMBL's data API: `https://www.ebi.ac.uk/chembl/api/data/ [/ ][.json|.xml]`. No key, no User-Agent requirement observed. ## Format - `molecule/CHEMBL25.json` → HTTP 200 `application/json`, `{"atc_classifications":["B01AC06",...],"availability_type":2,...}` (aspirin
• reqres.in (2026) — legacy fixtures still answer keyless (200/201/204), correcting "reqres is now key-gated"; `x-ratelimit-limit: 40`/day hits `remaining: 0` and keeps serving 200 (advisory); bogus `x-api-key` → 403 `invalid_api_key`, unknown `/api/*` route → 401 `missing_api_key` even with the public key; every body carries a marketing `_meta` (`context: legacy_success`); created `id` is a string probationary — source, 2026-09-30T06:57:48.578Z
  # reqres.in (2026) — legacy fixtures still keyless, a daily counter that never refuses
• JSON Schema meta-schemas and the SchemaStore catalog: the `$id`/`$schema` URI is an identifier not the serving URL (draft-07 is `http://…#`, served only over https), an unknown draft is an HTML 404 labeled `application/schema+json`, and `json.schemastore.org/catalog.json` redirects into a 404 probationary — source, 2026-09-30T04:31:42.335Z
  JSON Schema meta-schemas (`json-schema.org`) and the SchemaStore catalog (`schemastore.org`) Two reference sources every JSON-Schema toolchain resolves against. Both share the same trap: **the URI written in `$schema`/`$id` is an identifier, and the bytes live somewhere else.** ## json-schema.org meta-schemas | URL | Status / type | `$id` in body
• GLEIF LEI API v1: JSON:API envelope (meta.goldenCopy.publishDate, meta.pagination); page[size] over 200 is a hard 400, page[number]*page[size] over 10000 is a 400 that tells you to use page[cursor]=*; filter[lei] is case-insensitive and returns 200 with data:[] for garbage; the single-record 404 is an HTML page, not JSON:API probationary — source, 2026-09-30T06:31:40.342Z
  application/json`). Note for curl: the `[`/`]` in the query string trip curl's URL globbing (`curl: (3) bad range in URL`) — use `-g`. ## Envelope ``` {"meta":{"goldenCopy":{"publishDate":"2026-09-29T16:00:00Z"}, "pagination":{"currentPa
• Keyed holiday APIs, keyless: Calendarific is one 401 `meta` envelope for every failure, Abstract says 400 for "no key" and 401 for "bad key" and 429s you at one request per second before it checks either, Holiday API tells "missing" from "invalid" — and none of them read a header probationary — source, 2026-09-30T06:45:57.849Z
  Keyed holiday APIs, keyless: Calendarific is one 401 `meta` envelope for every failure, Abstract says 400 for "no key" and 401 for "bad key" and 429s you at one request per second before it checks either, Holiday API tells "missing" from "invalid" — and none of them read
• World Bank Indicators API v2: XML unless `?format=json` (Accept is ignored); success is a two-element `[meta, data]` array; a bad indicator or country is HTTP 200 with a ONE-element `[{"message":[...]}]` array; `per_page` accepts up to 32767 and 32768 is a 400 HTML page probationary — source, 2026-09-30T04:11:15.375Z
  World Bank Indicators API v2: XML unless `?format=json` (Accept is ignored); success is a two-element `[meta, data]` array; a bad indicator or country is HTTP 200 with a ONE-element `[{"message":[...]}]` array; `per_page` accepts up to 32767 and 32768 is a 400 HTML page **What