Climavision
Climavision is a Louisville, Kentucky weather intelligence company that combines a proprietary nationwide supplemental network of low-altitude X-band, dual-polarization gap-filling weather radars with AI-driven numerical weather prediction (NWP) to deliver enterprise-grade forecasts and observational data. Its Horizon AI product line includes Horizon Point for site-specific forecasts, Horizon Global for ground-to-high- altitude global models, Horizon HI-RES for custom high-resolution local forecasting, and Horizon S2S for subseasonal-to-seasonal prediction. Climavision exposes a Weather API hosted at point-forecast-api.climavision.com with 1,800+ parameters, 15-day forecasts, and bearer-token authentication, plus a separate Radar Status API and Radar-as-a-Service offering that supplies Level II files, NetCDF, and GeoTIFF radar data products (reflectivity, velocity, dual-pol-derived QPE at 1km, precipitation type, tornado debris detection) for coverage below 4,000 feet where NEXRAD cannot see due to Earth curvature. The company integrates its radar feed into MRMS and has provided supplemental data into the National Weather Service's AWIPS software. Climavision processes 1.5+ billion datasets daily, serves customers across agriculture, aviation, commodity trading, drones and Advanced Air Mobility, energy and utilities, government, insurance and reinsurance, media, and transportation and logistics, and raised a $100 million strategic investment from TPG's Rise Fund. API access is gated through a sales-led contact process; no public sandbox or open-source SDKs are published, and the Climavision GitHub organization (github.com/Climavision) currently has only two minor public repositories (an archived Azure Table Storage helper and a GeoServer Helm chart fork).
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Climavision the way a machine reads it — 1 machine-readable artifact, 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 — Climavision scores 10.1/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 Climavision
Each block below is one kind of artifact we hold for Climavision. 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.
Security Posture 1
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.
Resources
Every other property we hold for Climavision — 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.
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 5
The organization behind the API
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/climavision · machine-readable index on apis.io