fshy

Home / Data APIs

NASA POWER

power.larc.nasa.gov/docs/services/Weather and solar data APIdata-apis/nasa-powerJSONcomparereport an errorprovider JSON

Free allowance
Free, keyless REST API for global solar and meteorological data (hourly, daily, monthly and climatology levels; daily series from 1981); no numeric request quota is published, the vendor says there is no set rate limit and usage is monitored.
Verdict
★ qualifiesusable as stated; the read path was probed
Cost
free tier
Identity
anonymousno card, no phone
Binding limit
per-object-cap20 parameters per single-point request on the daily API, 15 on the hourly API, 1 per regional request
Evidence
measured20 sources; a live request was made and its output kept
Freshness
stale on 2027-01-02checked 2026-11-02 (live); stale on 2027-01-02
Free tierFree, keyless REST API for global solar and meteorological data (hourly, daily, monthly and climatology levels; daily series from 1981); no numeric request quota is published, the vendor says there is no set rate limit and usage is monitored.
unit requests; metered on request-count; A single point takes up to 20 parameters on the daily API and 15 on the hourly API; regional requests take one parameter. Bulk path: the complete datastore is in public S3 buckets (s3://nasa-power as Zarr, s3://power-datastore as NetCDF, us-west-2), read with no AWS account, which bypasses the API's rate, transfer and timeout limits. Recent meteorological values are replaced by climate-quality values within 2 to 3 months.
Pricenone stated
Limits
  • request-rate unverified: no numeric limit is published; the vendor says there is no set rate limit and usage is limited to support equitable access source
  • per-object-cap (binding) 20 parameters per single-point request on the daily API, 15 on the hourly API, 1 per regional request source
Bindingper-object-cap No request rate is published, so the parameter cap per request is the number that shapes a large pull; the S3 buckets have no such cap.
Identityanonymous No sign-up and no key: keyless API calls and anonymous bucket listings answered HTTP 200; the AWS registry page says no AWS account is required.
EgressJSON, CSV, NetCDF and ASCII answers; the S3 buckets are free of charge to everyone
Per-object cap20 parameters per single-point request on the daily API, 15 on the hourly API, 1 per regional request
Retentionnot applicable: the unit is a request
Interfacerest, s3 REST over HTTPS GET at power.larc.nasa.gov/api/temporal/{daily,hourly,monthly,climatology}/{point,regional}, with OpenAPI pages; Zarr and NetCDF files in anonymous S3 buckets
Toolingany HTTP client; any S3 client reads the buckets with no signing; Python tutorials for Zarr access are published by the project
Composes withA keyless solar and reanalysis-based weather source for coordinates worldwide; use the S3 Zarr store for bulk pulls instead of looping the API.
ReliabilityRepeating the same location or flooding with synchronous requests can get an application blocked; overload answers HTTP 429.
NotesBulk path: s3://nasa-power (Zarr analysis-ready store) and s3://power-datastore (NetCDF).
Evidence notemeasured A keyless daily point call and an anonymous bucket listing were made and kept; the rate limit is not published and was not driven.
Parsed numbers
  • has-free-tier 1
Evidence 20
datesourcewhat it proved
2026-11-02power.larc.nasa.gov/docs/services/api/temporal/daily/daily API caps parameters per request
2026-11-02power.larc.nasa.gov/docs/services/api/temporal/hourly/hourly API caps parameters per request
2026-11-02power.larc.nasa.gov/docs/services/api/temporal/daily/repeating a location can get an application blocked
2026-11-02power.larc.nasa.gov/docs/tutorials/service-data-request/api/too many synchronous requests can be blocked
2026-11-02power.larc.nasa.gov/docs/services/api/the API answers 429 when overloaded
2026-11-02forum.earthdata.nasa.gov/viewtopic.php?t=4273no set rate limit; usage is monitored and limited for equitable access (answer of 2023-05-22)
2026-11-02github.com/ropensci/nasapower/issues/57a 2021 reply of the POWER team, relayed by a third party, gave 30 requests a minute on the climatology endpoint
2026-11-02power.larc.nasa.gov/docs/services/aws/the API has rate, transfer and timeout limits
2026-11-02power.larc.nasa.gov/docs/services/aws/the S3 buckets bypass the API limits
2026-11-02power.larc.nasa.gov/docs/services/aws/the AWS datastore is free to everyone
2026-11-02registry.opendata.aws/nasa-power/the buckets are read with no AWS account
2026-11-02registry.opendata.aws/nasa-power/anonymous listing of the Zarr bucket
2026-11-02registry.opendata.aws/nasa-power/no restriction on access or download
2026-11-02registry.opendata.aws/nasa-power/daily history from 1981
2026-11-02registry.opendata.aws/nasa-power/near-real-time lag
2026-11-02probe: https://power.larc.nasa.gov/api/temporal/daily/pointa daily point call with no key and no sign-up answered daily T2M values
2026-11-02probe: https://power.larc.nasa.gov/api/temporal/daily/pointthe call answered HTTP 200
2026-11-02probe: https://nasa-power.s3.us-west-2.amazonaws.com/an anonymous ListObjectsV2 on s3://nasa-power listed the MERRA-2 prefix
2026-11-02probe: https://nasa-power.s3.us-west-2.amazonaws.com/the anonymous bucket listing answered HTTP 200
2026-11-02raw.githubusercontent.com/public-apis/public-apis/master/REAlisted under Weather in public-apis with no auth