Hourly-resolution forecasts, global coverage, and a license built for production — not a side project bolted onto someone else's data feed.
Pick a city to see the same response your app would get from /v1/forecast/daily.
Live forecast data.
Every response is JSON, every field is documented, and nothing is deprecated without six months' notice.
Read the API docscurl "https://api.weathercore.org/v1/forecast/daily" \
-H "Authorization: Bearer $WEATHERCORE_KEY" \
-G --data-urlencode "lat=-1.2921" \
--data-urlencode "lon=36.8219" \
--data-urlencode "days=16"
const res = await fetch(
"https://api.weathercore.org/v1/forecast/daily" +
"?lat=-1.2921&lon=36.8219&days=16",
{ headers: { Authorization: `Bearer ${WEATHERCORE_KEY}` } }
);
const forecast = await res.json();
import requests
r = requests.get(
"https://api.weathercore.org/v1/forecast/daily",
params={"lat": -1.2921, "lon": 36.8219, "days": 16},
headers={"Authorization": f"Bearer {WEATHERCORE_KEY}"},
)
forecast = r.json()
For building and testing. For shipping to real users, see licensing below.
These plans cover using WeatherCore data inside your own product — not offering our API, or a service built on top of it, to other developers or businesses. See our Terms of Use.
The usage plans above cover building and testing. Once WeatherCore data ships inside something you sell, you need one of these three agreements.
For teams embedding WeatherCore forecasts directly into a shipped product — app, device, or platform. Removes shared rate limits and adds contractual support terms.
Rebrand the forecast engine as your own. No WeatherCore attribution in your product, your own domain on API responses, your own docs.
For agencies and platforms distributing WeatherCore access to their own client base under a revenue-share agreement.
Requesting terms opens the licensing calculator with your license pre-selected, where you can pick a payment term and request an invoice. No sign-in needed. Calculate your price
Keys, usage, and invoices in one place — no separate billing portal to log into.
Open the full dashboardA usage plan controls how many calls you can make. A license governs how you're allowed to use the data commercially — inside a shipped product, under your own brand, or resold to your customers. Most teams need both: a usage plan for volume, a license for permission.
Yes, under a White-Label License. You get a custom domain for API calls and can rename fields in the response schema to match your own product's vocabulary.
Yes — the Developer plan gives 1,000 calls a day against current conditions and a 7-day forecast, free indefinitely. It's scoped to non-production use.
You get sub-account keys to issue to your own clients, usage is tracked per sub-account, and you're billed at a wholesale rate with the difference to list price as your margin. Terms are set per partner.