Helipaddy sites vs ProblemsByVin

Helipaddy's Partner API returns nearby helicopter, EVTOL, and drone landing sites — hotels, aerodromes, pubs, and B&Bs with helipads — as JSON, gated to a per-partner category allow-list. A live GET and OPTIONS preflight against its real API host, helipaddy.com/wp-json/hp-partner/v1/sites, both echoed access-control-allow-origin back with the request Origin, resolving the stored "unknown" cors to "yes"; the GET returned a "hp_partner_api_invalid_key" 401 error, reconfirming auth "API Key" over HTTPS. Partner tokens are issued manually via WhatsApp/email under a negotiated agreement with no public self-serve tier — paid.

ProblemsByVin's Data Center publishes derived, CC BY 4.0-licensed datasets built from NHTSA's owner-complaint and recall record — a reliability scorecard, failure-mileage quartiles, and post-warranty failure patterns — as weekly-refreshed CSV and JSON downloads plus a machine-readable /data/catalog.json manifest. A live GET against both the docs page and the catalog endpoint returned access-control-allow-origin: *, reconfirming cors "yes"; no key was required, reconfirming auth "None" over HTTPS. The datasets are free to use, republish, and remix with attribution — free.