# SYNTHORA endoflife.date Product EOL Cycles

> SYNTHORA endoflife.date Product EOL Cycles is a paid API for AI agents from endoflife-product-cycles.hergertsynthora.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns the full support and end-of-life lifecycle for a named software product, including all release cycles, LTS flags, EOL dates, and latest patch versions.

## Facts

- Endpoint: POST https://endoflife-product-cycles.hergertsynthora.com/service
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthora-endoflife-date-product-eol-cycles-9c770f56
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZOBZO8gXQLR7zF2S6v08r

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability synthora-endoflife-date-product-eol-cycles-9c770f56 -d '<json body>'
```

Example prompt: Can you look up the full end-of-life lifecycle for Node.js — I need to see every release cycle, which ones are LTS, their EOL dates, and the latest patch version for each?

## When to prefer this

Use this endpoint when an agent needs structured, machine-readable EOL and LTS lifecycle data for a specific software product — particularly for automated compliance checks, dependency auditing, or upgrade planning pipelines. Prefer this over manual web scraping of endoflife.date because it provides a clean JSON response suitable for agent-to-agent workflows. It is best suited for single-product lookups where the product name is known.

## Known failure modes

- Unknown or misspelled product name returns empty or error result
- Product not tracked by endoflife.date returns no data
- Network timeout on the upstream endoflife.date service
- Invalid input schema (missing 'product' field) causes request failure
- Payment failure via x402 protocol blocks the request

## How this service works

Returns the full support/EOL lifecycle for a product (languages, runtimes, OS, databases, frameworks) from keyless endoflife.date: each release cycle with release date, LTS flag, EOL date, and latest patch. Lets autonomous agents flag end-of-life runtimes and drive agent-to-agent upgrade planning and compliance. Ranking surface for EOL risk. First 3 calls FREE per wallet — send header X-WALLET: 0x<addr>. No charge on upstream failure.

## Output

A JSON object containing the full set of release cycles for the requested product, with each cycle including its release date, whether it is LTS, the EOL date, and the latest patch version available. The response also includes an 'ok' boolean and a niche identifier.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "product": {
   "type": "string",
   "description": "product"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "niche": "endoflife-product-cycles",
  "result": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthora-endoflife-date-product-eol-cycles-9c770f56/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from endoflife-product-cycles.hergertsynthora.com](https://www.zero.xyz/host/endoflife-product-cycles.hergertsynthora.com/llms.txt)