OPEN-SOURCE DEVELOPER INFRASTRUCTURE UWA V1 RELEASE

Integrate once.
We handle the providers.

One open-source, self-hosted weather API gateway for multiple providers. Bring your keys; UWA routes each location and dataset to eligible sources, returns consistent schemas, and falls back when permitted.

Check provider eligibility
Location × Category × Capability routing Bring your own provider keys MIT-licensed · Self-hosted on Linux & Windows
FIG 01 / ONE INTEGRATION ILLUSTRATIVE MODEL
200 OK · CANONICAL

Choose a location to see how one API contract routes to an eligible upstream.

GET /v1/weather?lat=21.21&lon=81.43 SELECT A ROUTE ↓
COORDINATES & INPUT ELIGIBLE SOURCE OUTPUT
INBhilai, India
21.21, 81.43 · Weather
OpenWeather Rank #1 · Global policy
weather.v1 fallback: false
DEBerlin, Germany
52.52, 13.40 · Forecast
Bright Sky / DWD Rank #1 · Germany grid
forecast.v1 25 km drift gate
USNew York, USA
40.71, -74.01 · Alerts
US NWS Alerts Rank #1 · US polygon
alerts.v1 US-only policy
SELECTED ROUTEBhilai → OpenWeatherGlobal policy · Output: weather.v1
NORMALIZED
WHEN THE FIRST SOURCE FAILS Try the next eligible provider for that category → return the same schema
Simulate in Explorer ↓
ONE CLIENT API → MULTIPLE UPSTREAMSFALLBACK
BY POLICY

Release scope note · UWA v1 ships a hardened default lean_v1 production profile alongside full_experimental adapters for development and testing. Live upstream certification and operator acceptance remain separate checks.

View v1 release boundary
EXPLORE EVERYTHING / UWA V1

Every data capability.
One integration.

Request multiple categories in a single call with GET /v1/datasets or call individual category endpoints directly.

View limits & eligibility
MULTI-CATEGORY & DAILY ROUTESCombined /v1/datasets & daily forecast summaries (/v1/forecast/daily)

Fetch multiple categories in one call with 207 Multi-Status partial-availability support, or query sampled UTC daily forecast summaries.

View /v1/datasets View daily endpoint
THE ENGINE BEHIND THE CONTRACT

Infrastructure features, exposed—not buried.

Capabilities shown here describe source implementation, not performance certification.

Source ≠ live: Eight product families and ten protected routes are implemented in source. In the default lean_v1 production profile, current weather, forecast, daily forecast, geocoding, astronomy and /v1/datasets are active, while air quality, history, marine and alerts are gated under full_experimental for development/test. Read the v1 release boundary.

03 / THE PROBLEM

You integrate UWA. UWA integrates the providers.

Instead of wiring brittle point-to-point weather SDKs, unit converters, and fallback loops into every application, connect once to a single self-hosted gateway.

N×M INTEGRATION BURDEN
Your App Coupled to every vendor

Fragile complexity at every edge

Every upstream API forces your app to manage separate credentials, units, coordinate rules, rate limits, and outage fallbacks.

  • Client code breaks when a provider changes schema or goes down
  • Keys & vendor quotas duplicated across every microservice
1 CONTRACT · BYOK
Your App GET /v1/datasets
UWA V1 GATEWAY
Policy & 95% Quota Deterministic Router Normalizer + Drift Guard
OpenWeather Bright Sky US NWS Open-Meteo

Integrate once. Configure upstreams.

Your app calls one MIT-licensed endpoint. UWA filters eligible providers by location and category, handles failover, and returns one canonical schema.

  • Zero provider-specific parsing or failover logic in client apps
  • Server-side BYOK secrets with 25–50 km drift & 2h freshness gates
04 / HOW IT WORKS

A provider choice for each location and category. One schema per product.

Ask for Bhilai, Berlin or New York with the same client integration. Each requested dataset is routed independently; the response contract stays consistent for its product type.

01

Location

Accept coordinates or resolve an unambiguous place name via strict geocoding

02

Eligibility

Check which upstreams support that data category, coordinate coverage, quota and policy

03

Ranking

Choose the highest-ranked eligible provider per category using explicit deterministic rules

04

Attempt

Call the selected upstream, enforce 25–50 km coordinate drift and 2h freshness bounds

05

Fallback

If it fails, try the next eligible source for those coordinates and category

06

Response

Return a stable canonical schema (or 207 Multi-Status bundle) with source attribution

05 / EXPLORE THE ROUTE

Understand the decision, not just the result.

Change a location (Bhilai, Raipur, Berlin, London, New York), product, policy or failure and see how the illustrative trace changes.

A teaching simulation—not a benchmark, vendor availability check or Go runtime preview.

LOCAL INTERACTIVE MODEL

Routing Explorer

Faithful browser simulation of UWA’s Go DecisionEngine, providerpolicy catalog, 95% quota gate, and /v1/datasets bundler. Zero network calls.

Source-accurate model
TRY A SCENARIO
Advanced controls release profile, policy & failure cases
DECISION ENGINE RESULT — —
—
    06 / DEVELOPER EXPERIENCE

    One integration.
    Readable requests.

    Use the self-hosted Universal Weather API to request data by coordinates. The gateway selects eligible upstream providers, applies configured policy and normalizes the result to a versioned schema.

    01Bring your keysProvider secrets remain on your server.
    02Route per datasetIndependent selection and eligible failover.
    03One contractSource attribution and stable schemas.
    UWA / API WORKBENCHExplore the request → response
    SELF-HOSTED
    ONE REQUEST · ONE LOCATION

    Ask for current weather and 24 forecast points for the same coordinates.

    TERMINAL · GET /v1/datasets
    curl -H "X-API-Key: YOUR_GATEWAY_KEY" "http://127.0.0.1:8080/v1/datasets?datasets=weather,forecast&lat=21.21&lon=81.43&forecast.points=24"
    Scoped gateway key required200, 207 & error handling
    API CONTRACT

    /v1/datasets requests multiple categories for one location. A 200 OK means all requested categories succeeded; 207 Multi-Status preserves successful datasets and reports per-category errors when only some succeed. These examples do not contact live providers.

    View canonical schemas
    TECHNICAL ANSWERS

    Weather API gateway, explained.

    All questions

    What is Universal Weather API?

    UWA is an MIT-licensed, self-hosted weather API gateway. Applications call consistent endpoints while the server selects configured providers by location and data category, validates responses and returns versioned output contracts.

    Read the introduction

    How is a weather provider selected?

    UWA evaluates data capability, geographic eligibility, release profile, policy, credentials, health and quota before ranking eligible upstreams. Only suitable providers are candidates for each request.

    Learn about routing

    What happens when a provider fails?

    For classified failures, the gateway can try another eligible provider for that same dataset and location. Successful responses retain the canonical schema and include provenance and fallback metadata.

    Explore fallback behavior
    07 / PROVIDER GOVERNANCE

    Transparent by configuration.

    The v1 codebase includes 15 provider adapters across products. Each remains subject to credentials, licensing, coverage, release profile and verification.

    Inspect the provider matrix
    PROVIDER / RULESV1 PROFILE SNAPSHOT
    01OpenWeatherCurrentv1 core · Key + budget
    02MET NorwayForecastv1 core · Opt-in + UA
    03Bright Sky / DWDForecastExperimental · Germany
    04US NWS AlertsAlertsExperimental · US polygon
    15 ADAPTERS IN SOURCE ≠ 15 LIVE-CERTIFIED PROVIDERS
    08 / SYSTEM RELIABILITY

    If the preferred source fails, try the next eligible one.

    Your application continues calling the same endpoint. When the preferred provider fails or violates freshness/coordinate-drift bounds, UWA tries the next eligible candidate for those coordinates and category.

    Location and permissions first

    Only eligible sources enter a routing decision, even during outages.

    Bounded execution & integrity

    Retries, circuit breakers, 25–50 km drift ceilings and 2h observation age checks protect output quality.

    Provenance & partial resilience

    The response envelope explains the provider, fallback/cache state, and per-category 207 partial availability.

    09 / SELF-HOSTED CONTROL

    One integration.
    Your keys.
    Your server.

    Deploy UWA under the MIT license on your own infrastructure. Supply your own upstream keys and configure which services and release profile you operate. Your application speaks only to the gateway.

    CONTROL PLANE / OPERATOR OWNED
    LICENCEMIT open-source gateway
    CREDENTIALSBYOK secret store
    POLICYLocation · category · quota
    DEPLOYMENTLinux · Windows · container
    NO HOSTED LOGIN. NO BUILT-IN BILLING. NO LLM RUNTIME.
    11 / V1 RELEASE BOUNDARY

    Ship what’s verified.
    Label what isn’t.

    This website documents the UWA v1 release architecture and source contracts. Production infrastructure and live vendor acceptance remain separate operator gates.

    01 / V1 CORE (LEAN_V1)Hardened default public contract

    Current weather, hourly & daily forecasts, geocoding, astronomy and /v1/datasets multi-category orchestration.

    02 / EXPERIMENTAL PROFILEDev & test extended adapters

    Air quality, historical ERA5 reanalysis, marine wave grids, US NWS alerts and regional forecast adapters via full_experimental.

    03 / OPERATOR ACCEPTANCELive infrastructure certification

    Real PostgreSQL 16 & Redis 7 deployment, BYOK vendor terms, country polygons and native Linux/Windows service verification.

    BEHIND THE PROJECT

    A gateway with a story behind it.

    Explore the journey, motivation and open-source development behind Universal Weather API.

    Meet the creator
    READY TO EXPLORE?

    Understand your sources.
    Own your integration.

    Begin with verified v1 request shapes and deployment prerequisites.

    Search local documentation. No external requests.

    ↑↓ to move · Enter to openESC to close