# dep.halowerk.com Release Cadence Calculator

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

Calculates release intervals and inactivity periods for a package based on current registry timestamps

## Facts

- Endpoint: POST https://dep.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/dep-halowerk-com-release-cadence-calculator-953690cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JFlP_10c5J_Dg33P04TV6

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 dep-halowerk-com-release-cadence-calculator-953690cb -d '<json body>'
```

Example prompt: What's the release cadence and inactivity period for the 'express' package on npm — how often does it ship and when was the last release?

## When to prefer this

Use this endpoint when you need structured, derived release cadence and inactivity metrics for a specific package in npm, PyPI, crates.io, or Maven Central — particularly when you want transparent methodology disclosure and explicit flagging of unavailable fields rather than raw registry metadata. Prefer this over general package metadata endpoints when the specific question is about release frequency or maintenance activity.

## Known failure modes

- Package not found in the specified ecosystem — returns null fields with unavailable_fields populated
- Ecosystem registry temporarily unavailable — may return partial data or error
- Invalid ecosystem enum value — validation error returned
- Package name too long or empty — schema validation failure
- Insufficient release history to compute interval — relevant fields returned as null

## How this service works

Calculates release intervals and inactivity from current registry timestamps. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age. 

## Output

Returns computed release cadence metrics including average release interval, time since last release (inactivity), and methodology disclosure. Source-backed values include the registry source, time window, and data age. Fields that cannot be computed are returned as null and listed in an unavailable_fields array.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "maxLength": 300,
   "minLength": 1,
   "description": ""
  },
  "ecosystem": {
   "enum": [
    "npm",
    "pypi",
    "crates",
    "maven"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dep-halowerk-com-release-cadence-calculator-953690cb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dep.halowerk.com](https://www.zero.xyz/host/dep.halowerk.com/llms.txt)