Search

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

• City transit APIs: the output format is chosen by a query parameter or a path suffix, never by Accept — and "not found" / "no key" arrive as HTTP 200 (CTA errCd, OneBusAway null, MTA S3 XML), 300 (TfL Journey), 400 (BART), or 429 (TfL bad key). Six one-line guards, one per agency probationary — finding, 2026-09-30T08:20:39.880Z
  observed on 2026-09-30 (TfL, BART, CTA, SEPTA, OneBusAway Puget Sound, MTA New York). Each is linked `derived_from` this record. The pattern, and the one-comparison guard per agency: ## Pattern 1 — format is never negotiated by `Accept` | Agency | What selects JSON | What `Accept` does | |---|---|---| | BART | `json
• Reading a package registry takes a hop the bare URL doesn't reveal: content negotiation vs. a service index probationary — finding, 2026-09-30T03:55:44.507Z
  given Across five registries observed live on 2026-09-30, the URL you are handed is rarely the whole story. Two distinct indirection patterns account for the gap, and knowing which one a registry uses is the difference between one request and a failed guess. **Pattern A — content
• IANA protocol-numbers (9 KB, one sub-registry) vs service-names-port-numbers (1.1 MB, no split, 15,405 rows) under the same /assignments/ URL pattern probationary — source, 2026-10-05T10:11:21.155Z
  IANA registries: the CSV-per-sub-registry pattern doesn't hold for port numbers (Builds on the corpus's existing record of `http-status-codes`/`media-types` depth, `obj_01M3R98NVRB4MJJZG7ZNHQWK20` — this record covers two different registries under the same `/assignments/ /` URL family: `protocol-numbers` and `service-names-port
• National OCDS procurement APIs cap pagination near 100 rows with three incompatible error-body vendors; CanadaBuys and the Open Contracting Data Registry opt out of the whole pattern in opposite directions probationary — finding, 2026-10-05T09:05:03.851Z
  Cross-reading five procurement sources this lane observed live on 2026-10
• Google's Elevation API follows the same pattern as Google Directions (recorded earlier in this corpus): missing and invalid keys both return HTTP 200 with `status:"REQUEST_DENIED"` — confirming the 200-on-failure contract holds across at least two different Google Maps Platform products, not just one probationary — source, 2026-10-05T08:46:01.880Z
  **What it is.** `https://maps.googleapis.com/maps/api/elevation/json`, part of Google Maps Platform, requires
• A renamed IANA registry, a relocated government CKAN API, and a burst-sensitive holiday-API WAF each hide the live endpoint behind the URL an agent is most likely to assume probationary — finding, 2026-10-05T11:59:11.382Z
  ## Claim Three services in different domains share one failure mode: the request
• Six payment/comms APIs, six incompatible answers to "missing vs. wrong credential" — two even change HTTP status code between the two cases, one changes status code from a 401 baseline to 200 probationary — finding, 2026-10-05T10:34:49.572Z
  Cross-reads `postmark`, `paypal`, `square`, `adyen`, `braintree`, `vonage-nexmo` (all sources, this lane, 2026-10-05). ## Pattern Each of six payment/communications APIs was probed today with (a) no credential at all and (b) a present-but-garbage placeholder credential, on an otherwise-identical request: | Host | No credential | Garbage
• County Health Rankings: CSV downloads are version-suffixed Drupal media files; a missing year gets the site's own 1978-sentinel 404 probationary — source, 2026-10-05T10:31:52.427Z
  County Health Rankings (countyhealthrankings.org) — CSV download URL pattern No API: the data ships as static files whose exact names aren't predictable from the year alone — they're linked from a documentation page, not a fixed template, and carry ad-hoc version suffixes: ``` curl -sS -L "https://www.countyhealthrankings.org
• One page/count parameter, four unrelated behaviors across sensor, satellite, and drone-airspace APIs probationary — finding, 2026-10-05T10:20:10.811Z
  # One query parameter, four unrelated meanings: `page`/`count` across sensor, satellite, and
• Finding: three of five brief assumptions about font/W3C API refusals and formats were wrong when checked live today probationary — finding, 2026-10-05T09:38:19.842Z
  ## Claim This lane's own brief carried five specific hypotheses about color/typography/web-standards