# Paket Package Version History

> Paket Package Version History 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).

Returns the full, semantically-sorted version history of a package across seven ecosystems, including publication timestamps, deprecation status, and registry default flags.

## Facts

- Endpoint: POST https://paket.halowerk.com/v1/package-versions
- 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-package-version-history-5498941d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mr2H75mmTSAS1xtEoDHay

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-package-version-history-5498941d -d '<json body>'
```

Example prompt: Give me the full version history of the 'axios' npm package — sorted by semantic version — including when each version was published, which one is the registry default, and whether any are deprecated.

## When to prefer this

Choose this endpoint when you need a complete, semantically-correct version history of a package rather than just the latest version. It is especially valuable when naive alphabetical or registry-order sorting would mislead (e.g. 1.10.0 vs 1.9.0), when you need to identify deprecated versions and their reasons, or when you need to work across multiple ecosystems using a single normalized schema. Prefer it over raw registry APIs when correctness of semver ordering matters for downstream automation.

## Known failure modes

- Unknown package name returns 404 or empty version list
- Unsupported ecosystem returns validation error
- Registry temporarily unavailable causes upstream timeout
- Malformed package identifier returns 400 bad request
- Payment failure via x402 blocks the request before execution

## How this service works

Returns the full version history of a package from a single normalised schema that covers seven ecosystems. Versions are ordered by semantic version, not alphabetically and not in registry order, so 1.10.0 sorts after 1.9.0 — the mistake that quietly breaks naive comparisons. For each version you get the publication timestamp, whether it is the registry default, whether it is deprecated and the deprecation reason as the registry states it.

## Output

A normalized, semantically-sorted list of all released versions of the specified package, each entry containing: version string, publication timestamp, whether it is the registry default, whether it is deprecated, and the deprecation reason if applicable. Covers seven package ecosystems under a single unified schema.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "maxLength": 300,
   "minLength": 1,
   "description": "Package name. Maven uses groupId:artifactId, Go uses the module path."
  },
  "limit": {
   "type": "integer",
   "default": 200,
   "maximum": 500,
   "minimum": 1,
   "description": "How many versions to return, newest first."
  },
  "system": {
   "enum": [
    "npm",
    "pypi",
    "maven",
    "go",
    "cargo",
    "nuget",
    "rubygems"
   ],
   "type": "string",
   "description": "The package ecosystem."
  },
  "include_prereleases": {
   "type": "boolean",
   "default": true,
   "description": "Whether pre-release versions appear in the list. They are counted either way."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paket-package-version-history-5498941d/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)