🌦️ 441 Weather API
Classified weather data for agents: every value carries its status — OBSERVED, MODEL, COMPUTED, FORECAST, INFERRED or UNCONFIRMED — and its source. No invented data, ever.
Why this API
Most weather APIs silently mix real observations with model output. Here, every value is labelled: you always know whether a figure was measured, computed or only forecast — and by which source. The multi-model core cross-checks ECMWF IFS, GFS, GEM and ICON, plus ECCC GeoMet, the NWS and METAR where available.
OBSERVEDMODELCOMPUTEDFORECASTINFERREDUNCONFIRMED
API address
These addresses are machine interfaces (APIs): the root returns a technical message, which is normal. The calls below are used from a program, an agent, or a tool like curl.
Endpoints
| GET | /health | Service health — public, no key |
| GET | /sources | Status of the core's data sources — public, no key |
| GET | /weather?lat&lon | Classified weather for a point — x-api-key header required (0.01 SOL / call) |
Full machine documentation (OpenAPI): 441engine.com/openapi/weather.json
Copy-paste examples
No key (public):
curl https://meteo.441engine.com/health curl https://meteo.441engine.com/sources
With your key (example coordinates):
curl -H "x-api-key: YOUR_API_KEY" \ "https://meteo.441engine.com/weather?lat=48.42&lon=-71.07"
The response carries current conditions, the 24 h hourly forecast, a 24 h summary, computed signals and the status of each source. Possible errors: 401 (missing or invalid key), 429 (rate limit reached).
Get a key — payment
Access is paid per call: 0.01 SOL per /weather call, in SOL (or in $M441 with a 10% discount, i.e. a 0.009 SOL equivalent per call). Send the exact amount to the address below, then call the API with your payment signature (under 24 h old, never reused). The /health and /sources endpoints stay public and free.
Every payment is covered by our written guarantee, and verified purchases are published in the public log.