Receive & resolve
Validate auth scopes and input shape. Coordinates are used directly; place text can be resolved on weather, forecast and /v1/datasets when strict resolution is enabled.
Give UWA the coordinates (or an unambiguous place name) and one or more requested data categories. It evaluates eligible upstream providers for each category at that location, chooses according to configured rules, and returns a consistent schema with provenance—even when fallback is needed.
Validate auth scopes and input shape. Coordinates are used directly; place text can be resolved on weather, forecast and /v1/datasets when strict resolution is enabled.
Reject candidates blocked by product, geographic coverage, release profile, declared use, policy, credentials or 95% pre-flight quota gates.
Apply deterministic operator priority and measured health (10+ observations) to eligible providers; never rely on AI or opaque heuristics.
Fetch with direct-dial SSRF protection, validate 25–50 km coordinate drift and 2h observation age ceilings, and map to canonical schemas.
Recover from classified upstream or validation failures using the next eligible candidate for that category and location.
Return source attribution, cache/fallback status, request trace correlation, and 207 Multi-Status partial-failure detail on /v1/datasets.
Use this to understand how Geographic Location × Data Category × Provider Capability interact—not to check live vendor availability.
Faithful browser simulation of UWA’s Go DecisionEngine, providerpolicy catalog, 95% quota gate, and /v1/datasets bundler. Zero network calls.
Explicit boundary: the explorer intentionally uses a simplified browser-only rule set. To verify your live gateway, run gateway --check-config, uapctl doctor, and the Go integration test suite.