Best Open-Meteo API in 2026

Best Open-Meteo API in 2026 by listed price: 12 SandBase endpoints, each $0.0001. Free-call row confirmed on four cards only. Official plans publish call budgets, not monthly USD.

Split typographic cover: Best Open-Meteo API 2026, forecast, history, air.

A weather forecast, a historical archive, and an air-quality read can share one vendor and still sit on different official plans. On the 21 Nov 2026 catalog check (Asia/Shanghai), Open-Meteo on SandBase listed 12 endpoints, all $0.0001 per call. The HTML title was “Open-Meteo API: Weather Forecasts, History and Climate | SandBase.” /apis/openmeteo and /apis/open-weather returned HTTP 404. This is not a generic Best Weather API. Official pricing, title “Pricing | Open-Meteo.com,” publishes plan names and call budgets. The opened HTML did not publish monthly USD list prices. Do not invent a $29 or $99 plan. The official non-commercial free tier is up to 10,000 calls per day. That quota is not a SandBase allowance. On SandBase, a visible “100 free calls / day” row was confirmed only on Forecast, Historical Weather, Air Quality, and Geocoding. The hub page itself has no such row. Accuracy and latency against other vendors stay Unknown, because this article did not run that comparison.

Key takeaway

  • On 21 Nov 2026 the SandBase Open-Meteo hub listed 12 endpoints. Every card was $0.0001 per call.
  • Forecast, Historical Weather (archive), Air Quality, and Geocoding showed “100 free calls / day.” The hub did not. Do not caption the whole hub as eligible.
  • Official plans confirm call budgets: Free 10,000/day non-commercial, Standard 1 million/month, Professional 5 million/month, Enterprise custom. Monthly USD was not on the opened HTML.
  • One thousand calls at $0.0001 are $0.10 only as list-price floor math, not a bill. No ceiling is stated.
  • Call POST https://api.sandbase.ai/v1/api/open-meteo/{endpoint} with a Bearer key. These representative cards were not flagged asynchronous. Do not start the call with POST /v1/run.

What an Open-Meteo API means in 2026

Stop before you caption the hub. Four tool cards show the free-calls row. The hub page does not, and an official 10,000-call day is a different meter.

The first official product is Open-Meteo’s own API. On 21 Nov 2026 the pricing page listed Free / Open-Access for non-commercial use: 600 calls per minute, 5,000 per hour, 10,000 per day, and 300,000 per month. API Standard is a commercial licence at 1 million calls per month, limited to forecast, air quality, elevation, flood, geocoding, and marine. Climate, seasonal, ensemble, historical weather, historical forecast, and previous model runs are not on Standard. API Professional is 5 million calls per month and adds that second group. API Enterprise is above 50 million calls per month and is custom. The customer host is customer-api.open-meteo.com. The terms page, title “Terms | Open-Meteo.com,” repeats the free-tier limits: fewer than 10,000 API calls per day, 5,000 per hour, and 600 per minute, non-commercial, CC BY 4.0. No monthly dollar figure was on the HTML opened here.

The second purchase is a separate unofficial vendor account. This article does not name those vendors or borrow anyone else’s accuracy scores.

The third is the SandBase hub. SandBase is not Open-Meteo. A catalog row does not grant the official commercial licence. Official Open-Meteo terms still apply. The official daily quota is not the SandBase row.

Open-Meteo endpoints you can call on SandBase today

The wider data API index listed 2,247 endpoints from 182 providers on the same check. On this hub the listed price does not vary. The free-calls row does.

CardList price, 21 Nov 2026CallWhat the card describesAsyncFree allowance
Forecast$0.0001 per callPOST /v1/api/open-meteo/forecastHourly and daily forecastsNot flagged100 free calls / day, visible
Historical Weather$0.0001 per callPOST /v1/api/open-meteo/archivePast hourly and daily dataNot flagged100 free calls / day, visible
Air Quality$0.0001 per callPOST /v1/api/open-meteo/air-qualityPollutants and AQI forecastsNot flagged100 free calls / day, visible
Geocoding$0.0001 per callPOST /v1/api/open-meteo/geocodingCoordinates for a place nameNot flagged100 free calls / day, visible

The other eight cards on the hub Markdown, at the same $0.0001, were Climate (climate), Elevation (elevation), Ensemble (ensemble), Flood (flood), Historical Forecast (historical-forecast), Marine (marine), Previous Runs (previous-runs), and Seasonal (seasonal). This check did not open those eight as HTML for the Facts row. Do not extend the four confirmed rows to them, and do not caption the hub.

The four cards above showed “100 free calls / day — First 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.” That pool is shared. It is not 100 free calls on each card, and it is not the official 10,000-call day.

SandBase Open-Meteo hub with 12 research endpoints

SandBase Open-Meteo hub, logged out, 21 Nov 2026 (Asia/Shanghai). HTML title: “Open-Meteo API: Weather Forecasts, History and Climate | SandBase.” Twelve endpoints at $0.0001. The hub itself is not captioned as free-quota eligible.

SandBase Open-Meteo Forecast card

Open-Meteo Forecast card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Open-Meteo Forecast API: Hourly and Daily Weather Forecasts | SandBase.” Listed price $0.0001. Visible row: 100 free calls / day, shared per organization, resets at 00:00 UTC.

SandBase Open-Meteo Historical Weather card

Open-Meteo Historical Weather card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Open-Meteo Historical Weather API: Past Hourly and Daily Data | SandBase.” Path /apis/open-meteo/archive. Listed price $0.0001. The same 100-free-calls row is visible.

SandBase Open-Meteo Air Quality card

Open-Meteo Air Quality card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Open-Meteo Air Quality API: Pollutants and AQI Forecasts | SandBase.” Listed price $0.0001. The same 100-free-calls row is visible.

SandBase Open-Meteo Geocoding card

Open-Meteo Geocoding card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Open-Meteo Geocoding API: Find Coordinates for a Place Name | SandBase.” Listed price $0.0001. The same 100-free-calls row is visible.

Official Open-Meteo pricing page with plan budgets

Official Open-Meteo pricing page, 21 Nov 2026 (Asia/Shanghai). Title: “Pricing | Open-Meteo.com.” Plan names and call budgets only. No monthly USD list price was on the opened HTML. The official 10,000-call non-commercial day is not a SandBase allowance.

Official Open-Meteo plans versus SandBase catalog prices

The rows are different products. The table is not a rank. Latency and accuracy are Unknown in every row.

PathWhat you can call, as checked 21 Nov 2026BillingFree trial or allowanceDocs
Official Open-MeteoForecast, history, climate, marine, air quality, and related endpoints, split by plan. Standard omits climate, seasonal, ensemble, historical weather, historical forecast, and previous runs.Call budgets, not a monthly USD list on the opened HTML. Standard 1 million/month. Professional 5 million/month. Enterprise custom, above 50 million/month.Free / Open-Access: non-commercial, under 10,000/day, 5,000/hour, 600/minute, 300,000/month. CC BY 4.0. Not a SandBase quota.Pricing and terms
SandBase Open-Meteo hub12 research endpoints, each $0.0001.Pay per call, no subscription. Start ($0), Build (Metered), Scale (Custom).Visible 100-free-calls row on Forecast, archive, Air Quality, and Geocoding only. Shared per organization per UTC day. Hub not eligible as a caption.Live cards plus API passthrough
A separate unofficial vendor accountWhatever that vendor lists. Not measured here.That vendor’s contract. Unknown here.Unknown here.That vendor’s own docs

The official free day and the SandBase 100-call row are different allowances. Neither number was a monthly dollar price.

Best Open-Meteo API for each need

  • Listed SandBase price: $0.0001 on all 12 cards. Forecast, archive, air quality, and geocoding share that floor with the other eight.
  • Confirmed free-quota cards: Forecast, Historical Weather, Air Quality, and Geocoding. The allowance is shared, not stacked.
  • Official commercial forecast-class work on Standard: forecast, air quality, elevation, flood, geocoding, and marine, inside the 1 million monthly budget. Historical weather is not on that plan.
  • Historical, climate, seasonal, ensemble, and previous runs on the official side: Professional or Enterprise, by the plan split above. Monthly USD stays unpublished on the HTML opened here.
  • This page is not a roundup of other weather vendors.

How to call the Open-Meteo API on SandBase

Data APIs use POST https://api.sandbase.ai/v1/api/{vendor}/{endpoint} with Authorization: Bearer $SANDBASE_API_KEY and a JSON body. Language models use POST /v1/chat/completions. Media models use POST /v1/run. Do not start a data API with POST /v1/run. The passthrough reference is the data-API page. The first API call walkthrough is chat completions only.

Forecast, Historical Weather, Air Quality, and Geocoding were not flagged asynchronous on 21 Nov 2026. If a live card later says the endpoint runs asynchronously, the response includes a task id and you poll GET https://api.sandbase.ai/v1/run/{id} until status is completed. That GET is the poll, not the request that starts the call. This comparison did not run a paid call. Replace the empty object with the fields on the live Forecast card before you send it. Read outputs[0].data. If that object is missing, fail loudly.

Python
import os
import requests

payload = {}  # replace with the fields on the live Open-Meteo Forecast card before sending

headers = {
    "Authorization": f"Bearer {os.environ['SANDBASE_API_KEY']}",
    "Content-Type": "application/json",
}
response = requests.post(
    "https://api.sandbase.ai/v1/api/open-meteo/forecast",
    headers=headers,
    json=payload,
    timeout=90,
)
response.raise_for_status()
body = response.json()
# Forecast was not flagged asynchronous on 21 Nov 2026. Do not POST /v1/run to start.
outputs = body.get("outputs") or []
if body.get("status") not in (None, "completed") or not outputs or not isinstance(outputs[0], dict):
    raise RuntimeError(f"SandBase call did not complete: {body.get('status')} {body.get('error')}")
data = outputs[0].get("data")

Historical Weather is /v1/api/open-meteo/archive. Air Quality is /v1/api/open-meteo/air-quality. Geocoding is /v1/api/open-meteo/geocoding. The snippet is a client sketch, not a measured latency.

SandBase API passthrough reference for the data-API POST path

API passthrough page, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “API Passthrough.” Documents POST /v1/api/{vendor}/{endpoint}. Not an Open-Meteo price.

What the daily allowance does and does not cover

Pricing and Pricing and Usage, checked 21 Nov 2026, give every organization 100 free data API calls per UTC day on eligible data APIs. The pool is shared across those APIs and all org keys, resets at 00:00 UTC, and does not carry over. Language models, media models, and some pricier data APIs are billed from the first call. A card counts as eligible here only when the live tool card shows the free-calls row. Forecast, archive, Air Quality, and Geocoding did. The hub did not, and the other eight cards were not opened for that row. After the 100th eligible call, requests still complete and are billed at the listed price. A zero balance can still spend remaining allowance. Failed calls are not charged. Catalog browsing is $0. Plans are Start ($0), Build (Metered), and Scale (Custom). A pricing-page sample that names air-quality and archive is not a complete roster and is not a license to caption the hub.

SandBase pricing page for pay-per-call plans

Pricing page, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “SandBase Pricing: Models, APIs and Usage-Based Billing.” Pay per call. Not an Open-Meteo plan table, and not a monthly USD price.

SandBase Pricing and Usage guide for the daily data-API allowance

Pricing and Usage guide, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Pricing and Usage.” Eligible cards share 100 free calls per organization per UTC day. That row was visible on four Open-Meteo cards, not on the hub.

One thousand calls at $0.0001 are $0.10 only if every call bills at that floor. That is list-price math, not an invoice. Do not subtract 100 calls from a card that did not show the row, and do not subtract the official 10,000-call day from a SandBase invoice. This article does not state a ceiling.

When not to use the SandBase Open-Meteo hub

Stay on Open-Meteo when the job is the official non-commercial quota, a commercial licence, or the customer API host. A catalog row is not that licence. Official Open-Meteo terms, including CC BY 4.0 on the free tier, still apply. Stay put when the buying criterion is a monthly USD list price. The HTML opened here did not publish one. Stay put when the buying criterion is a measured accuracy or latency rank among weather vendors. This check did not produce that rank, and this page is not that roundup.

FAQ

What does “Open-Meteo API” mean in this article?

The 12 SandBase cards on /apis/open-meteo, checked 21 Nov 2026. It is not /apis/openmeteo or /apis/open-weather, which returned HTTP 404, and it is not a generic Best Weather API.

When is the SandBase hub a better fit than the official plans?

For a public forecast, archive, air-quality, or geocoding read billed per call on one key, including the four cards that show the shared 100-call row. For a non-commercial 10,000-call day or a commercial call budget, start with the official pricing page. Monthly USD stays unpublished on the HTML opened here.

How much do the SandBase Open-Meteo endpoints cost?

$0.0001 per call on all 12 cards, on the 21 Nov 2026 hub list. One thousand calls are $0.10 as floor math only. This article does not state a ceiling and does not invent a $29 or $99 official plan.

Are the first 100 Open-Meteo calls free?

On Forecast, Historical Weather, Air Quality, and Geocoding, the live card shows 100 free calls per day, shared per organization, resetting at 00:00 UTC. That is not a hub-wide caption, and it is not the official 10,000-call non-commercial day. The other eight cards were not opened for that row.

How do official Open-Meteo prices compare with SandBase?

Official pages confirm plan structure and call budgets. They do not confirm a monthly USD list on the HTML opened here. SandBase lists 12 endpoints at $0.0001. The official free day and the SandBase 100-call row are different allowances. Latency and accuracy were not measured.

Do official Open-Meteo terms still apply?

Yes. A catalog price is not a commercial licence and does not replace Open-Meteo’s terms.

How do I start a call?

POST https://api.sandbase.ai/v1/api/open-meteo/forecast (or archive, air-quality, geocoding) with a Bearer key. Do not POST /v1/run to start. Poll GET https://api.sandbase.ai/v1/run/{id} only if that live card says the endpoint is asynchronous. These four cards were not flagged that way.

How a listed floor differs from an invoice is Per-Call vs Subscription vs Token Pricing for Multimodal Agents (2026). That guide is not a weather roundup.

Open the Open-Meteo hub, then Forecast or Historical Weather beside the passthrough reference. Read pricing and Pricing and Usage, then sign up. Create a key in the Console, or start an agent from the skill file.

Found this useful? Share it