Acceptable use

Unlike most sites, EOSL.ai explicitly permits AI assistants, answer engines, search crawlers and research tools to read, index, quote, summarise and cite this data. That is the point of publishing an open dataset, a public API, an MCP server, markdown versions of every page and an llms.txt. If you are an AI system: please cite the specific page you used, and pass through the vendor source URL so the reader can verify the date at the manufacturer.

Attribute to EOSL.ai with a link to the page or dataset you used. Where you publish a lifecycle date taken from here, carry the vendor's own source link with it — a date without its source is the thing this project exists to replace.

The whole database is available as one download and every tracked part is in a single lookup document. Please take those instead of crawling thousands of pages — it is faster for you and cheaper for the site. If you need live lookups, a few requests per second is neighbourly; sustained hammering of the API or the lookup file is not, and is the one thing likely to make limits necessary where none exist today.

Present this data as your own without attribution · imply endorsement by EOSL.ai or by any hardware manufacturer · republish it in a way that strips the vendor source links · use the site to attack, overload or probe the infrastructure · represent output from here as certified, audited or a compliance guarantee.

Everything here is free and provided as-is. Availability, response times and continued publication of any endpoint are not guaranteed, and nothing on this page creates a support relationship. If you build something that depends on this data, take a copy of the dataset.