# Paket Release Cadence Analyzer

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

Analyzes the release timing history of a package to detect cadence anomalies — specifically long dormancy gaps and burst release clusters — and reports where the pattern breaks.

## Facts

- Endpoint: POST https://paket.halowerk.com/v1/release-cadence
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paket-release-cadence-analyzer-b66ff1a1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zInTinHY3fdGGeShAbp5d

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-release-cadence-analyzer-b66ff1a1 -d '<json body>'
```

Example prompt: Can you check the release cadence of the lodash npm package and flag any long dormancy gaps or burst release clusters in its history?

## When to prefer this

Use this endpoint when you specifically need to analyze release timing anomalies — dormancy gaps or burst clusters — rather than general maintenance health signals (use the maintenance scoring endpoint for that). Prefer this when you want to understand whether a package's release cadence has structurally broken down, whether an automated publish process may have misbehaved, or whether a long silence suggests effective abandonment.

## Known failure modes

- Package not found in the specified ecosystem — returns an error or empty findings
- Package has too few releases to establish a meaningful median interval
- Ecosystem not supported — returns a validation error
- Malformed package name input — returns a 400-level error
- Network or upstream registry timeout causing a 5xx response

## How this service works

Looks at when a package published, not how often, and reports where the pattern breaks. Three kinds of finding, which mean different things and are kept apart. A long gap: a silence several times the package own median interval, which suggests dormancy. A burst: several releases inside a short window, which is either emergency fixes or an automated publish loop that ran away, and the response gives the dates so the reader can tell.

## Output

A structured report with up to three categories of cadence findings: long dormancy gaps (silences several times the package's own median interval), burst clusters (multiple releases within a short window), and normal cadence confirmation. Burst findings include the specific dates so the caller can distinguish emergency fixes from runaway automation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "maxLength": 300,
   "minLength": 1
  },
  "system": {
   "enum": [
    "npm",
    "pypi",
    "maven",
    "go",
    "cargo",
    "nuget",
    "rubygems"
   ],
   "type": "string"
  },
  "sensitivity": {
   "enum": [
    "low",
    "normal",
    "high"
   ],
   "type": "string",
   "default": "normal",
   "description": "How far from the median counts as an anomaly. low = 5x median gap, normal = 3x, high = 2x."
  },
  "include_prereleases": {
   "type": "boolean",
   "default": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paket-release-cadence-analyzer-b66ff1a1/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)