paket.halowerk.com publishes 14 machine-payable endpoints over the x402 protocol, priced from $0.003 to $0.006 per call. Each was probed directly; the response code below is what it returned.
| Endpoint | Method | Price | Probe |
|---|---|---|---|
| /v1/artifact-hash | GET | $0.003 | 402 |
| /v1/dependency-bloat | GET | $0.005 | 402 |
| /v1/dependency-confusion | GET | $0.005 | 402 |
| /v1/dependency-graph | GET | $0.005 | 402 |
| /v1/deprecation-monitor | GET | $0.004 | 402 |
| /v1/lifecycle-check | GET | $0.003 | 402 |
| /v1/maintainer-pulse | GET | $0.005 | 402 |
| /v1/package-freshness | GET | $0.003 | 402 |
| /v1/package-match | GET | $0.004 | 402 |
| /v1/package-versions | GET | $0.003 | 402 |
| /v1/release-cadence | GET | $0.004 | 402 |
| /v1/runtime-compat | GET | $0.004 | 402 |
| /v1/typosquat-radar | GET | $0.006 | 402 |
| /v1/upgrade-path | GET | $0.004 | 402 |
Takes a file digest and answers which released package version it is. Useful for an artefact found in a container layer, a build directory or an attachment with no metadata attached. Hex and base64 in…
Scores how much a package costs to depend on, using the resolved graph rather than a guess. Four measurements: the number of transitive nodes, the maximum depth, how many packages appear at more than …
Takes the names your organisation publishes internally and checks each against the public registry of the same ecosystem. Three findings, kept apart because they call for different actions. Name is fr…
Returns the resolved dependency graph of one package version across seven ecosystems: every node with its ecosystem, name, resolved version, whether it is bundled, and its depth from the root. Depth i…
A monitor with memory. The first call stores a snapshot of the packages you name and returns the baseline, explicitly marked as such rather than reporting everything as new — a monitor that cries wolf…
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.dat…
Answers whether the project behind a package is still alive, from two sources with different roles. deps.dev supplies stars, forks, open issue count, the declared licence and the OpenSSF scorecard wit…
Turns the release history of a package into a maintenance signal an agent can act on. Four measurements go in: the age in days of the newest stable release, the median gap between the last ten release…
Resolves a package to the source projects it declares, with the provenance of each link stated. This is the honest way to answer whether two packages belong together: names repeat across ecosystems an…
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…
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 …
Normalises what a package version declares about where it can run. For npm that is the engines, os and cpu fields plus the declared package type and whether native build scripts are present; for PyPI …
Generates the typical misspellings of a package name and looks up every one of them in the registry. Generation rather than search is deliberate: most of the seven ecosystems have no search API, and t…
Turns "we are on 2.4.1 and want to be current" into an ordered list of stops. The rule it enforces is that no major version is skipped: going from 2 to 5 means stopping at the last release of 3 and th…