Open-Meteo Weather Scraper - Forecast & History
Pricing
from $0.55 / 1,000 forecast scrapeds
Open-Meteo Weather Scraper - Forecast & History
Scrape weather forecast and historical data for any list of cities or coordinates from Open-Meteo: daily and hourly temperature, precipitation, wind, humidity and more. Free source, no key, no browser.
Pricing
from $0.55 / 1,000 forecast scrapeds
Rating
0.0
(0)
Developer
Scrape Sage
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Open-Meteo Weather Scraper - Forecast & History
Get daily weather for any list of cities or coordinates from Open-Meteo. City names are geocoded automatically, and each row is one day for one place with max/min temperature, feels-like, precipitation, rain/snow, wind speed & gusts, UV index, sunrise/sunset and more. Forecast up to 16 days ahead and up to 92 days of recent history. Free source - no key, no browser.
What you get per location-day
| Field | Meaning |
|---|---|
locationName / country / region | Resolved place |
latitude / longitude / timezone / elevation | Coordinates and zone |
date | The forecast/history day |
tempMax / tempMin / feelsLikeMax / feelsLikeMin | Temperatures (°C) |
precipitationSum / rainSum / snowfallSum / precipProbabilityMax | Precipitation |
windSpeedMax / windGustsMax / windDirection | Wind |
weatherCode / uvIndexMax / sunrise / sunset / radiationSum | Conditions |
Input
{ "locations": ["Berlin", "Tokyo", "40.71,-74.01"], "forecastDays": 7 }
- Locations - city names (geocoded automatically) or
lat,loncoordinates, one per line. - Import from a file - paste a list, or link a public
.txt/.csv, a Google Sheet/Drive link, or an Apify key-value-store record. - Forecast days (1-16) and Past days (0-92) set the date range. Output fields trim the columns.
Leave everything empty and the run returns a small free sample so you can see the shape first.
Reliability
Reads the official Open-Meteo API - free, no key, no proxy, no anti-bot, plus the Open-Meteo geocoding API for place names. A run that returns nothing bills $0; a city that cannot be geocoded is reported and charges nothing.
Honest limits
- Daily aggregates. Each row is one day (max/min/sum values); it is not hourly or minute-level data.
- Geocoding picks the best match for a city name - pass
lat,loncoordinates when you need an exact spot.
Pricing
$0.001 per forecast day on the FREE tier (tiered pricing lowers it with volume). One row = one location per day; only rows actually saved are billed.
Output views
- Forecast - location, date, max/min temp, precipitation, wind and the weather code.
Use with AI assistants (MCP)
Available through the Apify MCP server - an agent can pull the week's weather for a list of cities to plan logistics, travel or events.
Agent-ready: autonomous payments (x402 & Skyfire)
This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:
- x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
- Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.
Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.