# Hardware End-of-Life Lookup: EOSL Status by Vendor/Product (`smilemask/hardware-end-of-life-lookup`) Actor

Search a dataset of 3,100+ vendor hardware product families (Cisco, Juniper, Dell, HPE and more) for category, end-of-service-life status and date, with links to the per-family detail page and vendor source bulletin. Free, keyless, source-linked, CC BY 4.0 dataset from EOSL.ai.

- **URL**: https://apify.com/smilemask/hardware-end-of-life-lookup.md
- **Developed by:** [돈벼락](https://apify.com/smilemask) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Hardware End-of-Life Lookup: EOSL Status by Vendor/Product

Search a dataset of 3,100+ vendor hardware product families (Cisco, Juniper, Dell, HPE and more) for category, end-of-service-life status and date, with links to the per-family detail page and vendor source bulletin. Free, keyless, source-linked, CC BY 4.0 dataset from EOSL.ai.

### What does Hardware End-of-Life Lookup do?

Search 3,100+ networking and IT hardware product families for end-of-service-life status and dates.

### What can you use it for?

- Audit a network/server vendor inventory for product families nearing end-of-service-life.
- Prioritise hardware refresh planning by status (past, soon, active).
- Look up a vendor's product category and EOSL status before a purchase.
- Feed asset-management or CMDB enrichment pipelines.

### Why use this Actor?

- **Fast and cheap:** lightweight HTTP-based Actor with no browser, so runs finish in seconds and cost very little.
- **No API keys or accounts needed** for the data source (see notes below).
- **Clean, structured JSON** that you can export as CSV, Excel, JSON or XML, or pull through the Apify API and integrations.
- **Scheduling, webhooks and integrations:** run it daily and send results to Google Sheets, Slack, Zapier, Make, n8n or your own API.

### Input

Configure the run in the **Input** tab (all fields have sensible defaults).

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `query` | string | no | - | Matches vendor, product family/series or category, e.g. cisco, catalyst, router. |
| `maxResults` | integer | no | `50` | Maximum number of product families to return. |

#### Example input

```json
{
  "query": "cisco",
  "maxResults": 50
}
```

### Output

Results are stored in the default dataset. Download them from the **Output** tab or via the API.

#### Example result

```json
{
  "vendor": "Cisco",
  "series": "6500 Series",
  "category": "Switch",
  "status": "past",
  "endOfServiceLife": "2009-11",
  "familySlug": "cisco-catalyst-6500",
  "url": "https://eosl.ai/system/cisco-catalyst-6500/",
  "detailUrl": "https://eosl.ai/api/v1/family/cisco-catalyst-6500.json",
  "datasetSource": "EOSL.ai open dataset (CC BY 4.0)",
  "scrapedAt": "2026-10-14T20:33:31.404Z"
}
```

#### Output fields

| Field | Type | Example |
|---|---|---|
| `vendor` | string | "Cisco" |
| `series` | string | "6500 Series" |
| `category` | string | "Switch" |
| `status` | string | "past" |
| `endOfServiceLife` | string | "2009-11" |
| `familySlug` | string | "cisco-catalyst-6500" |
| `url` | string | "https://eosl.ai/system/cisco-catalyst-6500/" |
| `detailUrl` | string | "https://eosl.ai/api/v1/family/cisco-catalyst-6500.json" |
| `datasetSource` | string | "EOSL.ai open dataset (CC BY 4.0)" |
| `scrapedAt` | string | "2026-10-14T20:33:31.404Z" |

### How much does it cost?

The Actor is billed by Apify according to the pricing shown on the **Pricing** tab of this page. Runs are small and fast, and the Apify Free plan includes monthly platform credits so you can try it at no cost. You can set a maximum cost per run, and the Actor stops cleanly when that limit is reached.

### Notes and limitations

- Data is EOSL.ai's open dataset (CC BY 4.0), rebuilt from vendor end-of-life bulletins.
- endOfServiceLife is a vendor-published month-granularity date (YYYY-MM); it is null when not yet announced.
- detailUrl links to the full per-family JSON record (SKUs, exact dates, source bulletins, replacements).
- Leave the search field empty to list entries in dataset order.

### Tips

- Start with a small test run, then scale up the input.
- Use **Schedules** to automate recurring runs and **Webhooks** or **Integrations** to deliver the data where you need it.
- Call the Actor from your code with the Apify API or the official JavaScript and Python clients.

### FAQ

**What do the status values mean?**

active = not yet end-of-sale, soon = end-of-service-life approaching, past = already past end-of-service-life, mixed = some SKUs in the family differ, unknown = not yet determined.

**Does this cover software end-of-life too?**

No, use the Software End-of-Life Tracker Actor for software/OS product lifecycles; this one is hardware product families.

### Feedback

Found a bug or need an extra field? Open an issue from the **Issues** tab of this Actor and it will be looked at quickly.

### More tools from the same author

- [Software End-of-Life Tracker: EOL Dates for 400+ Products](https://apify.com/SmileMask/software-end-of-life-tracker) - Check release cycles, support and end-of-life dates for Node.js, Python, Ubuntu, PHP and 400+ more products.
- [CISA Known Exploited Vulnerabilities (KEV): CVE Catalog Search](https://apify.com/SmileMask/cisa-known-exploited-vulnerabilities) - Search CISA's catalog of actively exploited CVEs by vendor, product or keyword with due dates and ransomware flags.
- [Docker Hub Image Stats: Pulls, Stars & Last Updated (Bulk)](https://apify.com/SmileMask/docker-hub-image-stats) - Bulk Docker Hub repository stats: pull counts, stars, last update, categories and size.

# Changelog

This Actor's version history is a separate document: https://apify.com/smilemask/hardware-end-of-life-lookup/changelog.md

# Actor input Schema

## `query` (type: `string`):

Matches vendor, product family/series or category, e.g. cisco, catalyst, router.

## `maxResults` (type: `integer`):

Maximum number of product families to return.

## Actor input object example

```json
{
  "query": "cisco",
  "maxResults": 50
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "cisco",
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("smilemask/hardware-end-of-life-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "query": "cisco",
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("smilemask/hardware-end-of-life-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "cisco",
  "maxResults": 50
}' |
apify call smilemask/hardware-end-of-life-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,smilemask/hardware-end-of-life-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KfLdKbBFmAvfQOyxG/builds/N23nxbR7JmP4vOVNL/openapi.json