Credits are the accounting unit for the Premium Weather API. Every call deducts credits depending on which data package you request and at which time resolution. At the approximately 8,000-credit average, 40,000 calls correspond to about 320 million credits, 150,000 calls to 1.2 billion and 500,000 calls to 4 billion. Credits exist so a lightweight current-conditions request is not priced the same as a compute-heavy ensemble forecast.

One value, for one variable, at one location, at one timestamp. For the Dataset API the calculation is variables times locations times hours. Five variables for ten locations across a full year is 438,000 datapoints.

Weather API Pricing | Plans, Credits & Costs

Q: I request several packages in one call. How is that counted?

Each package is accounted separately, so a call combining three packages deducts the sum of all three. One exception: if you request the same package at several resolutions, only the highest resolution is charged.

Q: What counts as a view for the Maps products?

One view or session is a user loading the map. Each view requests multiple tiles depending on zoom level, layers and selected variables, and we calculate with an average of 50 tiles per view. 30,000 views per month therefore corresponds to roughly 1.5 million tiles.

Q: How do I try the APIs before committing?

Contact our sales team and we will set up trial access for you. We arrange trial periods individually rather than offering one fixed window, because evaluating a single forecast endpoint and piloting several APIs across a production integration need very different scope and time. Tell us what you are building and we will match the trial to it.

Pricing About Us

Frequently Asked Questions

What is a credit?

Credits are the accounting unit for the our APIs in the backend. Every call deducts credits depending on which data package you request and at which time resolution. Your in plan in the Premium API converts directly: at the ~8,000-credit average, 40,000 calls ≈ 320 million credits, 150,000 calls≈ 1.2 billion, 500,000 calls ≈ 4 billion. Credits exist so a lightweight current-conditions request isn't priced the same as a compute-heavy ensemble forecast. While hovering the information icon on the respective API you will see the conversion for each endpoint.

Why do packages cost different amounts of credits?

The cost reflects the computation and data volume behind each package. Current conditions cost 4,000 credits, multimodel wind 8,000, solar ensemble and multimodel wind power 16,000. Time resolution matters too: the same package at daily resolution typically costs half its hourly rate. The full per-package table is in the API documentation.

I request several packages in one call. How is that counted?

Each package is accounted separately: A call combining three packages deducts the sum of all three. One exception: if you request the same package at several resolutions, only the highest resolution is charged.

What is a datapoint?

One value, for one variable, at one location, at one timestamp. For the Dataset API: variables × locations × hours. Five variables for ten locations across a full year is 5 × 10 × 8,760 = 438,000 datapoints.

What counts as a "view" for the Maps products?

One view (or session) is a user loading the map. Each view requests multiple tiles depending on zoom level, layers and selected variables. We calculate with an average of 50 tiles per view. 30,000 views/month therefore corresponds to roughly 1.5 million tiles.

Which product covers historical weather?

It depends on the shape of the request. Point-based history for a single variable at one location is part of the Premium Weather API and reaches back to 1940. Large extracts across many variables, locations or timesteps belong to the Dataset API. Long-term climate statistics and future projections are the Climate Data API. Actual sensor observations rather than model data come from the Measurements API.

What's the difference between measured and modelled historical data?

The Measurements API returns what weather stations actually recorded — real observations, with the coverage gaps and station-specific distortions that come with them. Historical data in the Premium Weather API is re-analysis: a model reconstruction that is gap-free, consistent, and available for any coordinate worldwide, including locations where no station has ever existed.

Maps Plugin or Tile API?

The Plugin is a ready-made map interface with time and layer control: You embed it and you're done, with no map development. The Tile API delivers raw raster or vector tiles for a fully custom integration with libraries such as Mapbox GL JS or Leaflet. Volume tiers are identical; the Plugin requires Silver support, the Tile API Gold.

How do I try the APIs before committing?

Contact our sales team and we'll set up trial access for you. We arrange trial periods individually rather than offering one fixed window, because evaluating a single forecast endpoint and piloting several APIs across a production integration need very different scope and time. Tell us what you're building and we'll match the trial to it.

Industries

Use Cases

Industries

Use Cases

Industries

Use Cases

Industries

Use Cases

Industries

Use Cases

Industries

Use Cases

Pricing plans

Premium Weather API

Weather Maps Plugin

Weather Maps Tile API

Dataset API

Measurements API

Warnings API

Climate Data API

City Climate API

Frequently Asked Questions