ZV-2026-0161 · 2026-08-18 · apiacre.com

apiacre.com: Type of latitude on data.us-weather-forecast changed number → unset.

breaking

What changed

Type of latitude on data.us-weather-forecast changed number → unset. Type of timezone on data.us-weather-forecast changed string → unset. Type of longitude on data.us-weather-forecast changed number → unset.

What to do

If your agents call apiacre.com, pin the new snapshot, patch the affected call sites, and let a green contract check confirm the fix. If you don't use the changed tools, nothing is required, but the rest of the ecosystem just learned about it at the same moment you did.

The redline

number
+  unset   data.us-weather-forecast
string
+  unset   data.us-weather-forecast
number
+  unset   data.us-weather-forecast
Return normalized day/night or hourly forecasts worldwide: NOAA/NWS is preferred within su…
+  Resolve a city/locality name from bundled GeoNames CC BY data or use exact coordinates, th…   data.us-weather-forecast
+  place  Optional field place was added to data.us-weather-forecast; may shift model behaviour.
+  latitude  Default of latitude on data.us-weather-forecast changed unset → null.
+  timezone  Default of timezone on data.us-weather-forecast changed "UTC" → null.
+  longitude  Default of longitude on data.us-weather-forecast changed unset → null.
latitude  Field latitude on data.us-weather-forecast is no longer required.
longitude  Field longitude on data.us-weather-forecast is no longer required.
Full apiacre.com changelog →JSON feedWatch this for my agents