Working with several weather providers means handling different response formats, credentials, limits, and coverage rules. I built Universal Weather API to put those decisions behind one self-hosted Go API.
A local client can request current weather like this:
curl -H "X-API-Key: $UAP_API_KEY" \ "http://127.0.0.1:8080/v1/weather?lat=51.5074&lon=-0.1278" The gateway checks the client’s scope, selects a provider allowed for that location and data type, validates the upstream response, and returns versioned JSON with source information. If an eligible source fails, it can try another within the configured limits.
The API also has routes for forecasts, daily forecast summaries, location search, astronomy, and combined datasets. Optional experimental adapters cover air quality, history, marine data, and US weather alerts. Supported upstream services include OpenWeather, WeatherAPI, LocationIQ, Geoapify, Open-Meteo, MET Norway, Bright Sky, the US National Weather Service, and Sunrise-Sunset.
A few limits matter: you bring your own provider credentials where required, review each provider’s terms, and set policies and request budgets. This is a self-hosted project, not a public hosted weather endpoint. Open-Meteo’s hosted free API is for noncommercial use.
The first public source preview is available now. Local tests and Windows/Linux CI passed, while production deployment checks are still in progress.
If you build weather apps or self-host APIs, I’d appreciate feedback: what would make the first setup easier for you?