fshy

Home / Data APIs

NASdisks Drive Data API

www.nasdisks.com/data/Open dataset API: NAS drive specifications and failure ratesdata-apis/nasdisks-drive-data-apiJSONcomparereport an errorprovider JSON

Free allowance
No signup, no key, no rate limit: two read-only GET endpoints return the whole dataset of 298 drives, 21 with a measured failure rate, as JSON or CSV.
Verdict
★ qualifiesusable as stated; the read path was probed
Cost
free tier
Identity
anonymousno card, no phone
Binding limit
noneno named constraint binds
Evidence
documented24 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-03checked 2026-11-02 (live); stale on 2026-12-03
Free tierNo signup, no key, no rate limit: two read-only GET endpoints return the whole dataset of 298 drives, 21 with a measured failure rate, as JSON or CSV.
unit unlimited; metered on none; Both endpoints are cached for an hour. The failure-rate fields come from Backblaze Drive Stats.
Pricenone stated
Limits
  • request-rate none stated: the data page says no rate limit, and 40 parallel keyless GETs of drives.csv all answered HTTP 200 source
Bindingnone No quota, key or rate limit is stated, and a 40-request parallel burst met no 429; the one-hour cache of both endpoints is the only limit on freshness.
Identityanonymous No signup and no key: the data page says so, and keyless GETs of both endpoints answered HTTP 200.
Egressnot applicable: a dataset API, not metered in bytes; both endpoints are cached for an hour
Per-object capno cap stated; the whole dataset is one 168410-byte JSON or one 28364-byte CSV
Retentionthe live endpoints serve the current catalogue, cached for an hour; dated snapshots of the dataset are kept in a GitHub repository and in a Zenodo deposit
Interfacerest HTTPS GET of https://www.nasdisks.com/data/drives.json (a top-level object with license, count and a drives array) and https://www.nasdisks.com/data/drives.csv (the same rows, flat), open to all origins; an OpenAPI 3.0.3 contract at https://www.nasdisks.com/openapi.yaml also covers a third endpoint, /embed/cheapest.json
Toolingany HTTP client, such as curl with jq; the data page gives a Zenodo DOI to cite the dataset
Composes withReference data on NAS and enterprise drives: specs, CMR/SMR recording technology and annualized failure rates derived from Backblaze Drive Stats, read as one JSON or CSV file. Bulk path: drives.json or drives.csv is the whole dataset in one GET, and dated snapshots of the dataset are in the GitHub repository deeddy/nas-drive-data and in a Zenodo deposit.
ReliabilityBoth endpoints are cached for an hour, so an answer can lag the catalogue; both answered HTTP 200 to keyless GETs on 2026-11-02.
NotesFree requests: no quota, no key. Rate limit: none stated. Bulk path: drives.json or drives.csv, the whole dataset in one GET, with dated snapshots in a GitHub repository and a Zenodo deposit. The failure-rate fields come from Backblaze Drive Stats.
Evidence notedocumented The data page states no signup, no key and no rate limit, and the repository README repeats no key and no rate limit; keyless GETs of drives.json and drives.csv answered 200 with the 298-drive count the page gives, and a 40-request parallel burst met no 429.
Parsed numbers
  • has-free-tier 1
Evidence 24
datesourcewhat it proved
2026-11-02www.nasdisks.com/data/part of the text of Evidence note, above
2026-11-02www.nasdisks.com/data/the dataset holds 298 drives, 21 of them with a measured failure rate
2026-11-02www.nasdisks.com/data/both endpoints are read-only GETs, open to all origins and cached for an hour
2026-11-02www.nasdisks.com/data/drives.json is a JSON object with license, count and a drives array
2026-11-02www.nasdisks.com/data/drives.csv carries the same rows as a flat CSV
2026-11-02www.nasdisks.com/data/an OpenAPI 3.0 contract at openapi.yaml covers both endpoints and a price feed
2026-11-02www.nasdisks.com/data/not published
2026-11-02www.nasdisks.com/data/the data page shows a plain curl call piped to jq as the way to read the endpoint
2026-11-02www.nasdisks.com/data/the data page names a Zenodo DOI to cite the dataset
2026-11-02probe: https://www.nasdisks.com/data/drives.jsona keyless GET of drives.json answered 200 with 168410 bytes
2026-11-02probe: https://www.nasdisks.com/data/drives.jsonthe answer carries Cache-Control max-age=3600, public
2026-11-02probe: https://www.nasdisks.com/data/drives.jsonthe answer allows cross-origin reads from any origin
2026-11-02probe: https://www.nasdisks.com/data/drives.jsonthe body states a count of 298 drives and holds a drives array
2026-11-02probe: https://www.nasdisks.com/data/drives.csva keyless GET of drives.csv answered 200 with 28364 bytes
2026-11-02probe: https://www.nasdisks.com/data/drives.csvthe CSV starts with a header row of the drive fields
2026-11-02probe: https://www.nasdisks.com/data/drives.csvthe burst was 40 parallel GETs
2026-11-02probe: https://www.nasdisks.com/data/drives.csvthe highest status of the 40 runs was 200, so none answered 429
2026-11-02www.nasdisks.com/openapi.yamlthe contract is titled NASdisks Drive Data API
2026-11-02www.nasdisks.com/openapi.yamlthe contract is OpenAPI 3.0.3
2026-11-02www.nasdisks.com/openapi.yamlthe contract has a third path, /embed/cheapest.json
2026-11-02github.com/deeddy/nas-drive-datathe repository README repeats that the live endpoints are cached, need no key and have no rate limit
2026-11-02github.com/deeddy/nas-drive-datathe repository keeps a dated JSON snapshot that mirrors the live API
2026-11-02github.com/deeddy/nas-drive-datathe repository files are dated snapshots, with the live dataset at nasdisks.com/data
2026-11-02zenodo.org/records/21225049a Zenodo deposit holds a dated JSON snapshot of the dataset