# dep.halowerk.com Deprecation Check

> dep.halowerk.com Deprecation Check is a paid API for AI agents from dep.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-18).

Checks whether a package in npm, PyPI, crates.io, or Maven Central is deprecated, yanked, or removed, returning registry metadata with source and age disclosure.

## Facts

- Endpoint: POST https://dep.halowerk.com/v1/deprecation-check?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dep-halowerk-com-deprecation-check-6e9ec509
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e9cWAgsD4m43iK2PVA6sC

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-deprecation-check-6e9ec509 -d '<json body>'
```

Example prompt: Can you check if the npm package 'request' is deprecated or yanked from the registry?

## When to prefer this

Use this endpoint when you need a definitive, source-backed answer on whether a specific package is deprecated, yanked, or removed from its registry. It is preferable to general package metadata endpoints when the specific concern is package withdrawal status, and better than manual registry inspection when you need machine-readable results with data provenance. It supports npm, PyPI, crates.io, and Maven Central in a single API.

## Known failure modes

- Package name not found in the specified ecosystem — fields returned as null
- Unsupported ecosystem value — validation error returned
- Registry temporarily unavailable — partial or null response with unavailable_fields populated
- Malformed request (missing name or ecosystem) — 400-level error
- Payment not completed — 402 response blocking access

## How this service works

Checks current registry metadata for deprecated, yanked or removed releases. 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 current registry metadata indicating whether the package is deprecated, yanked, or removed. Missing facts are returned as null with field names listed in unavailable_fields. Source-backed values include their source, time window, and data age; derived values disclose their derivation method.

## 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-deprecation-check-6e9ec509/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)