Schema drift watch
An API can return 200 OK and still break your code by renaming or dropping a field. On every check we fingerprint the response structure (field paths and types, ignoring values and nulls) and record any change. Free APIs change silently; this is where it shows.
Tracked shapes
Field paths per response, and changes seen since monitoring began
| Open-Meteo Forecast | 15 | stable |
| Open-Meteo Geocoding | 21 | stable |
| OpenStreetMap Nominatim | 15 | stable |
| Zippopotam.us | 9 | stable |
| Where the ISS at? | 13 | stable |
| World Bank Indicators | 4 | stable |
| USGS Earthquakes | 39 | stable |
| Nager.Date Holidays | 8 | stable |
| UK Carbon Intensity | 7 | stable |
| Wikipedia REST | 40 | stable |
| Open Library Search | 36 | stable |
| Coinbase Spot Price | 4 | stable |
| CoinGecko | 2 | stable |
| Binance Ticker | 2 | stable |
| Frankfurter FX | 5 | stable |
| ExchangeRate-API (open) | 12 | stable |
| GitHub REST | 1 | stable |
| npm Registry | 61 | stable |
| PyPI JSON | 58 | stable |
| httpbin | 9 | stable |
| JSONPlaceholder | 4 | stable |
| Hacker News (Firebase) | 1 | stable |
| PokéAPI | 291 | stable |
| Dog CEO | 2 | stable |
| Datamuse Words | 4 | stable |
Recent changes
No response-shape changes detected yet. Every successful check compares the JSON structure (field paths and types) against the last one; the first change will show up here with exactly which fields appeared or vanished.