Premium NASA POWER Hourly
1 creditGET /api/premium/climate/power/hourlyHourly-resolution NASA POWER data for one point. Same parameter codes as the daily endpoint but at hourly bins. Range capped at 30 days due to upstream payload size.
When to use this endpoint
For energy modeling, hour-of-day analysis, or agronomic decisions where daily averages lose the relevant signal.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| latitude* | query | number | WGS84 latitudee.g. 37.7 |
| longitude* | query | number | WGS84 longitudee.g. -122.4 |
| parameters* | query | string | Comma-separated parameter codese.g. T2M |
| start* | query | string | YYYYMMDDe.g. 20260501 |
| end* | query | string | YYYYMMDD (max 30 days from start)e.g. 20260530 |
| community | query | string | AG | RE | SBe.g. AG |
* required
Example response
{ "ok": true, "data": { "header": { "fill_value": -999 }, "properties": { "parameter": { "T2M": { "20260501-00": 11.4, "20260501-01": 10.9 } } } }, "billing": { "credits_charged": 1, "credits_remaining": 49 } }Code samples
Python SDK
tf._get("/premium/climate/power/hourly", latitude=37.7, longitude=-122.4, parameters="T2M", start="20260501", end="20260502", community="AG")TypeScript SDK
await fetch("https://tensorfeed.ai/api/premium/climate/power/hourly?latitude=37.7&longitude=-122.4¶meters=T2M&start=20260501&end=20260502", { headers: { Authorization: "Bearer tf_live_..." } });FAQ
Why is the range capped at 30 days?
Hourly resolution produces ~24x the payload of daily. NASA POWER is generous with rate limits but the response sizes get unwieldy past 30 days.