# dep.halowerk.com Package Metadata API

> dep.halowerk.com Package Metadata API is a paid API for AI agents from dep.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Retrieves current package metadata (version, description, dependencies, license, etc.) from npm, PyPI, crates.io, or Maven Central for a named package

## Facts

- Endpoint: POST https://dep.halowerk.com/v1/package-meta
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dep-halowerk-com-package-metadata-api-8c1f1ca7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A9GsU0c84_19Lz-jvpmSy

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-package-metadata-api-8c1f1ca7 -d '<json body>'
```

Example prompt: Can you pull up the current package metadata for 'express' on npm — I need the latest version, license, and any available dependency info?

## When to prefer this

Use this endpoint when you need authoritative, real-time package metadata from a specific open-source registry (npm, PyPI, crates.io, Maven Central) without scraping registry websites yourself. It is particularly useful for dependency auditing, license compliance checks, version pinning workflows, or enriching a software bill of materials (SBOM). Prefer it over general web search when you need structured, machine-readable metadata with explicit provenance and data-age disclosure.

## Known failure modes

- Package not found on the specified ecosystem — returns null metadata or error
- Invalid or unsupported ecosystem enum value — validation error
- Package name exceeds 300 characters or is empty — validation error
- Upstream registry (npm/PyPI/crates.io/Maven) is temporarily unavailable — may return stale or partial data
- Ambiguous package name with no exact match — returns null or closest match with unavailable_fields populated

## How this service works

Retrieves current package metadata from npm, PyPI, crates.io or Maven Central. 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

A JSON object containing current package metadata fields such as latest version, description, license, author, dependencies, homepage, and repository link. Missing facts are returned as null with their field names listed in an unavailable_fields array. Source-backed values include the data 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-package-metadata-api-8c1f1ca7/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)