Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in

Collectors · Research & science

Weather API in Python

Daily weather by place name — temperature, rain, wind; forecast and recent history. One POST from Python with the input, rows back as JSON with 28 fields, $0.0002 per delivered day. No proxies or parsers to maintain.

A Python requests snippet that posts {
A Python requests call to the weather_forecast collector returns one dict per day, at $0.0002 each.

First call

Install, call, read the rows.

pip install requests
The only dependency.
import os, requests

r = requests.post(
    "https://api.quanticdata.io/v1/scraper/collectors/weather_forecast/run",
    headers={"Authorization": f"Bearer {os.environ['QD_API_KEY']}"},
    json={

    },
    timeout=120,
)
r.raise_for_status()
run = r.json()["payload"]
print(run["count"], "rows,", run["cost"]["usd"], "USD")
for row in run["results"]:
    print(row.get("date"), row.get("weather"), row.get("weather_code"), row.get("temp_max_c"))
Python: one Weather (Open-Meteo) run, printing date, weather, weather_code, temp_max_c

The key comes from an environment variable, never from the code. The run answers in the same request when it finishes in time; payload.results holds the rows and payload.cost what they cost.

Request parameters

What the collector takes.

Input of the Weather (Open-Meteo) collector
ParameterTypeRequiredMeaning
locationstringnoCity or place name (geocoded).
latitudenumbernoExact latitude (skips geocoding).
longitudenumbernoExact longitude.
daysintegernoDays ahead (1-16).
past_daysintegernoRecent history to prepend (0-92).
max_resultsintegernoHow many days to deliver at most (1–30). You pay only for delivered days.

Response fields

28 fields per day.

Fields of each row (day)
FieldTypeWhat it holds
rankinteger1-based position.
datestringDay (YYYY-MM-DD, local time).
weatherstring, nullableConditions label.
weather_codeinteger, nullableWMO code.
temp_max_cnumber, nullableMax temperature °C.
temp_min_cnumber, nullableMin temperature °C.
precipitation_mmnumber, nullablePrecipitation sum, mm.
precipitation_probabilitynumber, nullableMax precipitation probability %.
wind_max_kmhnumber, nullableMax wind speed km/h.
locationstring, nullableResolved place name.
countrystring, nullableCountry.
latitudenumberLatitude used.
longitudenumberLongitude used.
feels_like_max_cnumber, nullableMaximum apparent temperature, °C.
feels_like_min_cnumber, nullableMinimum apparent temperature, °C.
rain_mmnumber, nullableRain, mm.
snowfall_cmnumber, nullableSnowfall, cm.
precipitation_hoursnumber, nullableHours with precipitation.
wind_gusts_kmhnumber, nullableMaximum wind gusts, km/h.
wind_direction_degnumber, nullableDominant wind direction, degrees.
uv_index_maxnumber, nullableMaximum UV index.
sunshine_hoursnumber, nullableHours of sunshine.
sunrisestring, nullableSunrise, local time of the place.
sunsetstring, nullableSunset, local time of the place.
regionstring, nullableFirst-level administrative region of the geocoded place.
country_codestring, nullableISO country code of the geocoded place.
elevation_mnumber, nullableElevation of the forecast grid cell, metres.
timezonestring, nullableIANA timezone of the place.

Add ?format=csv to the runs endpoint to get the same rows as CSV.

Long runs

Run in the background, then poll.

A run that needs more time can go to the background: send "async": true, get 202 with the run id, and poll the runs endpoint until the status is done. Reading a run is free.

import os, time, requests

H = {"Authorization": f"Bearer {os.environ['QD_API_KEY']}"}
r = requests.post("https://api.quanticdata.io/v1/scraper/collectors/weather_forecast/run", headers=H,
                  json={**{}, "async": True}, timeout=30)
run_id = r.json()["payload"]["run_id"]
while True:
    run = requests.get(f"https://api.quanticdata.io/v1/scraper/collectors/runs/{run_id}", headers=H, timeout=30).json()["payload"]
    if run["status"] in ("done", "failed"):
        break
    time.sleep(5)
print(run["status"], run["count"])
Python: background run and polling

Errors

What can come back, and what is billed.

Collector run errors
StatusMeaningBilled
400The input does not match the collector (payload.errors)No
401Missing or wrong API keyNo
402Balance and free credit do not cover the run: top upNo
422The input can never resolve; retrying the same input cannot helpNo
424The run failed at the source (blocked, timed out, layout changed); safe to retryNo
429Rate limit or a per-account brake; wait for Retry-AfterNo

Only delivered rows are billed: a run that delivers nothing costs nothing.

Price

$0.0002 per delivered day.

What Weather (Open-Meteo) rows cost at list price
RowsCost
1$0.0002
1,000$0.20
10,000$2.00

Up to 30 days per run; split larger jobs into several runs. The $2 free credit every month covers about 10,000 days. No subscription; paid tiers lower the unit price. All collector prices: collector pricing.

Before you run it

Questions developers ask

Is there a free Weather (Open-Meteo) API?

Every account gets $2 of free usage each month, about 10,000 days of this collector at $0.0002 each, with no card.

Do I have to handle proxies, retries or blocks?

No. The collector runs on our network and handles them; a run blocked at the source returns 424 and is not billed.

How many rows can one run return?

Up to 30 days per run (the max_results input, where the collector has one).

Can an AI agent run it?

Yes: the MCP server exposes it as the run_collector tool, with the same input and price. See the MCP server.

Run it on the free credit.

Create an API key, export it as QD_API_KEY and run the example. $0.0002 per delivered day, no subscription.