Data source
Data from Nexar / Octopart, delivered clean.
4 datasets pulled from Nexar / Octopart's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.
- 4 datasets
- 1 industry
- Real rows on request
What Datadory delivers from Nexar / Octopart
4Nexar API (Octopart) Data
LCSC Electronics Catalog
TME Electronic Components Catalog & API
FindChips Aggregated Price & Inventory Search
Pick a catch, see the rows.
Name any Nexar / Octopart dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.
Get a sampleAPI, files, or your warehouse. Daily, weekly, or hourly.
Straight answers about Nexar / Octopart data
What does Datadory deliver from the Nexar / Octopart source?
One Electronic Components dataset scored 9/10: one verified record per manufacturer part number with identifying fields, a commerce layer of named sellers carrying stock levels, price breaks, minimum order quantities and packaging forms, and engineering context - parametric specs, lifecycle status, estimated factory lead time and the best-ranked datasheet - on the same row.
How many components does the Nexar / Octopart dataset cover?
Millions - no exact public part count is published, which Datadory states plainly rather than inflating. The catalog serves global distribution with region-selectable scoping, and the sampled ESP8266EX record showing DigiKey at 6,433 units and $1.45 median at quantity 1,000 is a measured anchor, not a projection.
Which field identifies a part across systems?
The manufacturer part number. It keys every record internally and joins to vendor line items, internal BOMs and other distributor files without fuzzy matching - the cleanest join key in the industry. Batch-matching structures also resolve many part numbers in one pass for BOM-scale work.
Does the data include lifecycle status and lead times?
Yes to both. Lifecycle status rides in the parametric spec attributes beside stock and price, so active, obsolete and end-of-life flags become a filterable column, and estimatedFactoryLeadDays puts a number on arrival timing - 42 days on the sampled part - turning supply risk into arithmetic.