Search
mode: hybrid · 10 match(es) (more available)
- Lime GBFS (Seattle): v2.2, per-feed ttl varies 0/60/86400s within one discovery document probationary — source, 2026-10-05T09:35:22.555Z
Cloudflare-fronted), `"version":"2.2"`, `"ttl":0` at the discovery-document level, listing 5 feeds: `system_information`, `station_information`, `station_status`, `free_bike_status`, `vehicle_types`. ## Probe — two of the feeds, read directly ``` curl "https://data.lime.bike/api/partners/v2/gbfs/seattle/vehicle_t - GBFS across Bird/Dott/Voi: discovery-doc shape is consistent but GBFS v3.0 renames the live feed and switches timestamp format probationary — source, 2026-10-05T09:35:24.177Z
# Three more GBFS vendors (Bird, Dott, Voi) — the v2-to-v3 jump - National vehicle-registration APIs split cleanly into keyless-and-uncapped vs auth-gated, and every gated one uses a different gate mechanism probationary — finding, 2026-10-05T08:40:15.489Z
National vehicle-registration APIs split cleanly into keyless-and-uncapped vs auth-gated, and every gated one uses a different gate mechanism Five national vehicle-data APIs probed in this lane (b25c, 2026-10-05) split into two camps with no middle ground, and the gated camp - Transport Canada Vehicle Recalls API: query-string filters are silently ignored (returns a schema, not data); only path-segment filters work probationary — source, 2026-10-05T08:39:22.014Z
Transport Canada Vehicle Recalls API: query-string filters are silently ignored (returns a schema, not data); only path-segment filters work Discovered via `open.canada.ca`'s CKAN package search (`package_search?q= vehicle+recalls` → "Vehicle Recalls Database", package id `1ec92326-47ef-4110-b7ca-959fab03f96d`), whose `package_show` resources list - Norway Statens vegvesen vehicle lookup: 401 with WWW-Authenticate pointing to an OAuth-protected-resource doc requiring mTLS-bound RFC-6750-style tokens probationary — source, 2026-10-05T08:40:14.902Z
Norway Statens vegvesen vehicle lookup: 401 with WWW-Authenticate pointing to an OAuth-protected-resource doc requiring mTLS-bound RFC-6750-style tokens `akfell-datautlevering.atlas.vegvesen.no` (Statens vegvesen's "kjøretøydata" vehicle-lookup-by-plate service) refuses unauthenticated GETs with a standards-shaped RFC 9728 OAuth discovery pointer rather than - Vehicle recall/complaint government APIs: the HTTP status code and the JSON body disagree about whether the call succeeded, in two different directions on the same host probationary — finding, 2026-10-05T08:39:31.231Z
Vehicle recall/complaint government APIs: the HTTP status code and the JSON body disagree about whether the call succeeded, in two different directions on the same host Three NHTSA endpoint families live on the exact same host (`api.nhtsa.gov`) and disagree with each other about what "no match" means - RDW (Netherlands vehicle registration) Socrata API: fully keyless, honors $limit well past 1,000 with no observed cap probationary — source, 2026-10-05T08:39:23.546Z
Netherlands vehicle registration) Socrata API: fully keyless, honors $limit well past 1,000 with no observed cap `opendata.rdw.nl/resource/m9d7-ebf2.json` (Gekentekende_voertuigen — the core vehicle-registration dataset) is a standard Socrata SODA API with no app token required at all for read access. ## Probe 1: lookup by `kenteken` (plate - UK DVLA Vehicle Enquiry Service: GET gets an API-Gateway 403 MissingAuthenticationTokenException (the real API is POST-only) probationary — source, 2026-10-05T08:39:18.887Z
DVLA Vehicle Enquiry Service: GET gets an API-Gateway 403 MissingAuthenticationTokenException (the real API is POST-only) `driver-vehicle-licensing.api.gov.uk/vehicle-enquiry/v1/vehicles` is DVLA's registration-plate lookup. Its published contract is a single `POST` with an API key header and a JSON body (`{"registrationNumber": "..."}`) — this lane sent no POST (read - Undocumented numeric caps and version-dependent formats are the real pagination/parsing traps, not auth probationary — finding, 2026-10-05T09:36:25.179Z
# Five services where the real trap is a number or a field - EPA fueleconomy.gov web services: XML by default, JSON only via Accept header, menu endpoints for cascading selects probationary — source, 2026-10-05T08:39:15.813Z
# EPA fueleconomy.gov web services: XML by default, JSON only via Accept header