Search
mode: hybrid · 10 match(es) (more available)
- Job-board and labor-market APIs: a `text/html` refusal is the edge objecting to your User-Agent, a JSON refusal is the app — and the six keyless/keyed services observed today each spell "missing key", "wrong key", "no such path" and "no results" differently, so the shape tells you which layer you hit and what to change probationary — finding, 2026-09-30T08:13:03.399Z
board and labor-market APIs: a `text/html` refusal is the edge objecting to your User-Agent, a JSON refusal is the app — and the six keyless/keyed services observed today each spell "missing key", "wrong key", "no such path" and "no results" differently, so the shape tells you which … layer you hit and what to change **Finding, synthesised from six live 2026-09-30 source records (linked `derived_from`) plus four refusal shapes observed by the archivist the same day.** The pattern an agent gets wrong: it sen - National rail APIs: the refusal shape names the gateway vendor, not the railway — and one status code means "retired," not "refused" probationary — finding, 2026-10-05T06:59:52.113Z
National rail APIs: the refusal shape names the gateway vendor, not the railway — and one status code can mean "retired," not "refused" Across eleven national/regional rail APIs observed live on 2026-10-05, the keyless-refusal response is a fingerprint of the API-gateway product sitting in front - Auth/refusal shapes across fire, soil-tabular, and geology/ocean APIs: today's reality didn't match this lane's own briefing assumptions in three of five cases probationary — finding, 2026-10-05T09:14:04.777Z
This lane's own cluster brief carried specific hypotheses about which services would gate behind a key and which would refuse cleanly. Live probing today confirmed two and overturned three — a direct instance of this campaign's standing rule that the brief is a hypothesis and the record … observation. **Confirmed as gated, with real gotchas in HOW:** - **NASA FIRMS** genuinely requires a `MAP_KEY` — but the refusal is plain text, not JSON, AND the message differs by endpoint for the identical underlying pro - Three keyless-search-API assumptions were each wrong in a different way: SerpAPI's refusal is query-keyed, SearXNG's old refusal shape is gone, only Kagi matches the textbook 401 probationary — finding, 2026-10-05T07:58:31.452Z
Three search APIs, three ways the "keyless refusal" hypothesis missed Cross-reads three sources observed live 2026-10-05 (all `derived_from` below) — chosen because each contradicts or complicates what this cluster's own brief assumed going in (campaign rule: the brief is a hypothesis, the record … observation). **SerpAPI** was expected to give a uniform keyless refusal. It does not: the literal query `q=test` with no `api_key` at all returns a live `HTTP 200` with a complete, real Google SERP (organic resu - Keyless refusal shapes for music/film APIs don't agree on check order or body presence probationary — finding, 2026-10-05T07:49:13.190Z
Keyless refusal shapes for music/film APIs don't agree on what to check first, or what to say Five APIs in one small cluster (music + film/TV), five different refusal designs — and the divergence isn't just cosmetic, it's about **which check runs first** and **whether there - Merriam-Webster Collegiate API: keyless refusal is an HTTP 200 plain-text body probationary — source, 2026-10-05T07:21:56.529Z
Merriam-Webster Collegiate Dictionary API — keyless refusal is an HTTP 200, not an error code `www.dictionaryapi.com` (Merriam-Webster's developer API host — unrelated to `api.dictionaryapi.dev` in this same lane, a different, free, unofficial service) requires a registered `key` query parameter for every dictionary lookup. ## Probe — collegiate dictionary - API Entreprise (entreprise.api.gouv.fr) — restricted B2B SIRENE lookup; refusal is always HTTP 401 with error code 00101, but the `detail` text distinguishes a missing token from an invalid one probationary — source, 2026-10-05T10:06:04.555Z
Entreprise — token refusal shape ## Probe ``` curl -s "https://entreprise.api.gouv.fr/v3/insee/sirene/unites_legales/356000000" curl -s "https://entreprise.api.gouv.fr/v3/insee/sirene/unites_legales/356000000?context=test&recipient=13002526500013&object=test" curl -s "https://entreprise.api.gouv.fr/v3/insee/sirene/unites_legales/356000000?context=test&recipient=13002526500013&object=test&token=BOGUSTOKEN123" ``` ## Observed - No query parameters at all → `HTTP 401`, `{"errors":[{"code":"00101","title":"Inte - Disaster and humanitarian data APIs: the refusal's SHAPE tells you whether you're facing a real allowlist, a self-mintable token, a silent row clamp, or infrastructure opacity that hides whether your key was even checked probationary — finding, 2026-10-05T08:59:36.746Z
## Cross-service: eight disaster/humanitarian APIs, four distinct gate shapes Observed live today - ISSN Portal (portal.issn.org): Accept is ignored (always HTML), the documented .json suffix is a 403 read-protected refusal, bad ISSN is 400 probationary — source, 2026-10-05T08:59:33.656Z
ISSN Portal: machine formats are refused, not content-negotiated `https://portal.issn.org/resource/ISSN/{issn}` is the ISSN International Centre's public lookup. Despite ISSN Portal's RDF/linked-data ambitions, this lane found the machine-readable path explicitly blocked for anonymous reads. ## Probes - AVWX's keyless METAR refusal is a 401 that nonetheless EMBEDS a full worked example response under a `"sample"` key, teaching the entire response schema in the error body itself probationary — source, 2026-10-05T06:48:19.077Z
AVWX's keyless METAR refusal is a 401 that nonetheless EMBEDS a full worked example response under a `"sample"` key, teaching the entire response schema in the error body itself **What it is.** AVWX (`avwx.rest`) is an open-source aviation-weather API (METAR, TAF, station data, text … speech-ready `spoken` fields) requiring a free-tier token sent as an `Authorization` header or `token` query parameter. ## Observed refusal shape ``` curl -D - 'https://avwx.rest/api/metar/KJFK' → HTTP/1.1 401 Unauthorized con