Xweather
Xweather, a Vaisala company, provides weather data APIs delivering science-backed, hyper-local weather intelligence for operational applications. The Xweather Weather API exposes current conditions, forecasts, severe weather alerts, lightning data, air quality, observations, wildfire information, tropical cyclone tracks, and maritime weather through a single REST API. Authentication uses a client_id and client_secret passed as query parameters or HTTP headers.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Xweather the way a machine reads it — 64 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Xweather scores 58.1/100 (developing), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Xweather
Each block below is one kind of artifact we hold for Xweather. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Xweather Air Quality API
Air quality index and pollutant data
Xweather Alerts API
Severe weather alerts and warnings
Xweather Conditions API
Current and historical weather conditions
Xweather Fires API
Wildfire data
Xweather Forecasts API
Weather forecasts
Xweather Lightning API
Lightning strike data and nowcasts
Xweather Maritime API
Marine and ocean weather data
Xweather Observations API
Weather station observations
Xweather Tropical API
Tropical cyclone and hurricane data
Scroll within the panel for all 9 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Xweather Weather API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Xweather Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Xweather Finops
FINOPSFeatures 9
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Real-Time Conditions
Current surface weather observations for any location worldwide.
Hourly and Daily Forecasts
Forecast records out to 15 days with hourly and daily granularity.
Severe Weather Alerts
Government-issued alerts, watches, and warnings with severity, urgency, and certainty.
Global Lightning Network
Cloud-to-ground and in-cloud lightning strike data from Vaisala's global detection network.
Lightning Threat Nowcast
Probabilistic short-term lightning threat used to drive stop-work and all-clear automation.
Air Quality
AQI values, primary pollutant, and detailed pollutant breakdowns for monitoring and reporting.
Maritime Weather
Marine weather including waves, swell, sea-surface temperature, and sea state.
Wildfire Data
Active wildfire incident records and perimeters for situational awareness.
Tropical Cyclones
Active tropical cyclone tracks, intensity, and forecast cones.
Scroll within the panel for all 9 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Xweather Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Xweather API Rules
SPECTRALXweather API Rules
SPECTRALJSON Schema 17
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AirQualityObservation
JSON SCHEMAAirQualityResponse
JSON SCHEMAAlert
JSON SCHEMAAlertsResponse
JSON SCHEMAConditionsObservation
JSON SCHEMAConditionsRecord
JSON SCHEMAConditionsResponse
JSON SCHEMAFiresResponse
JSON SCHEMAForecastPeriod
JSON SCHEMAForecastsResponse
JSON SCHEMALightningResponse
JSON SCHEMALightningStrike
JSON SCHEMALightningThreatsResponse
JSON SCHEMALocation
JSON SCHEMAMaritimeResponse
JSON SCHEMAObservationsResponse
JSON SCHEMATropicalCyclonesResponse
JSON SCHEMAScroll within the panel for all 17 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Xweather Weather Api Structure
JSON STRUCTUREExamples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Xweather Get Alerts Example
EXAMPLEScroll within the panel for all 7 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 7
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Construction Lightning Safety
Automatically pause and resume outdoor construction work using lightning threat nowcasts.
Aviation Ground Operations
Drive ramp closures and re-openings around lightning, severe weather, and visibility thresholds.
Outdoor Sports and Events
Manage stadium and event evacuations and re-entries based on lightning and severe weather.
Energy and Utilities
Plan grid operations, crew dispatch, and storm restoration around forecasts and alerts.
Logistics and Routing
Optimize routing and dispatch decisions using maritime, road weather, and severe weather feeds.
Insurance and Risk
Use historical and real-time storm and lightning data for claims and underwriting.
Environmental Reporting
Aggregate AQI and pollutant feeds for ESG and regulatory reporting.
Scroll within the panel for all 7 ·
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
AerisWeather Mapping
Tile and overlay services for visualizing Xweather data on web and mobile maps.
Vaisala Lightning Network
Underlying global lightning detection infrastructure feeding the Xweather lightning APIs.
Common Alerting Protocol
Severe-weather alert payloads align with CAP severity, urgency, and certainty fields.
METAR
Surface observations are derived from the international METAR observation standard.
Resources
Every other property we hold for Xweather — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 9
Reference material describing how the API behaves
Scroll within the panel for all 9 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 3
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/xweather · machine-readable index on apis.io