eosl.ai
homeConnections

Get the data into your own tools

Everything on this site is available outside it: a free JSON API, a live MCP server for AI assistants, the full dataset under CC BY 4.0, published integrations for the tools that already hold your inventory, and feeds you can subscribe to. No account, no key, no rate gate.

Live data

JSON API

Every product and part number as JSON, plus one-line spreadsheet cells for Sheets and Excel. Machine-readable description at /openapi.json; one-file data plane at lookup.json.

/api/ →
Full dataset

Every part number with its dates and the vendor bulletin behind each, as CSV or JSON. CC BY 4.0: use it commercially, credit EOSL.ai.

/dataset/ →

AI assistants

MCP server

Five lookup tools over the live database for Claude, and any other MCP-capable assistant. An unknown part returns found:false, never a guess. Every page here also serves markdown to an Accept: text/markdown request, and /llms.txt maps the site for crawlers.

/mcp/ →

In the tools that hold your inventory

NetBox, Ansible and Snipe-IT

Three published integrations audit the inventory you already keep against this database: a NetBox plugin, an Ansible collection and a Snipe-IT CLI. Each is one fetch per run, read-only, and open source.

/integrations/ →

Feeds and embeds

Lifecycle change ledger

Every new product and changed date from the weekly re-read of the vendor sources, with an RSS feed.

/changes/ →
EOSL calendars

Per-vendor .ics feeds: subscribe in Outlook or Google Calendar and support-end dates appear as events.

/calendar/ →
Status badges

A copy-paste badge for a README or wiki showing a product’s live support status.

/embed/ →

Quick starts

Check one part from anything that speaks HTTP
curl https://eosl.ai/cell/ws-c3850-24t-l.txt
Give an AI assistant the database
claude mcp add --transport http eosl https://eosl.ai/mcp
Audit a whole inventory in one request
curl https://eosl.ai/data/lookup.json
Attribution for the dataset is one line: “Data: EOSL.ai” with a link. The API and MCP server need nothing at all. If you build something on this data, the integrations page shows the pattern the published tools use.