# Paket Lifecycle Check

> Paket Lifecycle Check is a paid API for AI agents from paket.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Given a product identifier and optional version, returns end-of-support dates, days remaining, LTS status, and latest patch for that release line.

## Facts

- Endpoint: POST https://paket.halowerk.com/v1/lifecycle-check
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paket-lifecycle-check-ed11af70
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Anm-Gqg3Xu28GTbDtUreT

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 paket-lifecycle-check-ed11af70 -d '<json body>'
```

Example prompt: Check the lifecycle status of Node.js 18 — I need to know if active support is over, how many days until end of life, whether it's an LTS line, and what the latest patch version is.

## When to prefer this

Use this endpoint when an agent needs precise, structured lifecycle data for a specific product and version — including days-remaining calculations and LTS classification — rather than raw release history or general package metadata. Ideal for compliance checks, upgrade planning, and automated EOL alerting workflows.

## Known failure modes

- Unknown product identifier returns an error or empty result
- Version string does not match any known release line
- Product exists on endoflife.date but version is ambiguous or malformed
- Network timeout reaching the endoflife.date data source
- Payment authorization failure for the $0.003 USDC x402 charge

## How this service works

Answers the question an agent actually has about a product cycle: for the version in use, is support over, how many days remain, and where should it move. Given a product identifier from endoflife.date and optionally a version, it locates the matching release line and returns the release date, the end of active support, the end of life, the end of extended security support where one exists, whether the line is an LTS line, the latest patch release within that line and the number of days to each…

## Output

Returns for the matching release line: release date, end of active support date, end of life date, end of extended security support (if applicable), whether it is an LTS line, the latest patch version within that line, and the number of days remaining to each milestone.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "product": {
   "type": "string",
   "maxLength": 80,
   "minLength": 1,
   "description": "Product identifier as used by endoflife.date, e.g. nodejs, python, postgresql, ubuntu, debian, redis."
  },
  "version": {
   "type": "string",
   "maxLength": 40,
   "description": "The version in use, e.g. 20.11.1. Without it every cycle is returned."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paket-lifecycle-check-ed11af70/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from paket.halowerk.com](https://www.zero.xyz/host/paket.halowerk.com/llms.txt)