This is the measure by which you are charged for the API service. It is made up of requests x variables x points.

• variable: wave.height x point = 1 API units

• variables: (air.temperature.at-2m, cloud.cover) x point = 2 API units

• variables: (wave.height, air.temperature.at-2m, cloud.cover) x 2 points = 6 API units

You receive a base number of API units based on your subscription plan, after these base units have been used you are then charged for each additional API unit (in lots of 100) up to the absolute limit you set in the "USAGE & KEYS" section of your account, found in the console.

Derived variables (calculated from other variables) don't count as units themselves, but you are charged for the underlying input variables required to calculate them. For example, requesting wind.speed charges for 2 units (the u and v components).

A full break down of the individual models available in each plan can be found once logged into the API Console

Our API doesn't just serve a single forecast model. It automatically selects the best available model for your specific location based on a multi-factor ranking system configured by our expert meteorologists. The system prioritizes models with:

• Higher priority - Set by forecasters based on model reliability

• Finer spatial resolution - Smaller domains with more detailed local coverage

• Better temporal resolution - More frequent forecast updates

For requests covering multiple time periods, the API can seamlessly join data from multiple models to give you the best coverage across your entire forecast horizon.

Yes, you can use the Starter plan for prototyping, testing, and building a proof of concept. However, once your integration is live or used in a production environment, you must upgrade to at least the Basic plan ($30/month) to ensure compliance with our commercial use terms.

Cycle locking ensures all data in your response comes from the same model run. Without this, you could get data from different forecast cycles that might be inconsistent with each other, for example, temperature from the 6am run and wind from the 12pm run. This feature is critical for scientific applications and safety-critical decision-making where data integrity is paramount.

All plans include 5 days of historical forecast data for validation, analysis or recovery. If you need long-term historical archives or hindcast data for research or modeling purposes, please contact our sales team at nzsales@metservice.com to discuss custom solutions.

Route forecasting is designed for applications where the location changes over time, like ships, aircraft, or delivery vehicles. You provide a series of waypoints with times (or a path with speed/direction), and we calculate the weather conditions along that entire journey. This is far more efficient than querying hundreds of individual points and ensures you get a cohesive forecast for the entire route.

• Starter: API access will be paused until the next billing cycle

• Paid Plans: Overage charges apply automatically at the rates shown above, or you can upgrade to the next tier for better value

A custom limit can be set in the API Console

Yes, you can upgrade your subscription at any time. Your currently subscription will be cancelled, and you will be charged the full price for the new plan, not considering the remaining time in your billing cycle. Your billing cycle and renewal date will change.

No, you will be charged only for the amount used. The cap will prevent accidental excessive charges (maximum to be used/charged will be the limit set).

MetOcean was acquired by MetService in 2013. This API wasn’t part of the original technology migration but we plan to do so in future.