# npm Package Metadata Lookup

> npm Package Metadata Lookup is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Returns normalized metadata for any npm package including current version, license, dependency list, and deprecation status without parsing the full registry response.

## Facts

- Endpoint: POST https://x402.forgemesh.io/node-package-metadata
- 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/npm-package-metadata-lookup-023417c7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6f59BczirlIbtUE7FMuLG

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 npm-package-metadata-lookup-023417c7 -d '<json body>'
```

Example prompt: Can you pull up the normalized metadata for the 'express' npm package — I need the current version, license, dependency list, and whether it's been deprecated?

## When to prefer this

Use this endpoint when an AI agent needs quick, structured npm package metadata (version, license, deps, deprecation) without having to download and parse the full verbose npm registry JSON. Ideal for dependency auditing, license compliance checks, or deciding whether to install a package.

## Known failure modes

- Package name not found in npm registry — returns error indicating unknown package
- Package name field missing from request body — returns validation error
- npm registry upstream unavailable — returns timeout or service error
- Typo in package name returns no results or wrong package metadata

## How this service works

Returns normalized metadata for any npm package, current version, license, dependency list, and whether it's been deprecated, without needing to parse the full, much larger raw registry response. For agents auditing a project's dependency tree or deciding what to install.

## Output

A normalized JSON object containing the package's current version, license identifier, list of dependencies, and a deprecation flag — extracted from the npm registry and pre-parsed so the agent doesn't need to handle the full raw registry payload.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "description": "package name, e.g. express"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "name": "express",
   "license": "MIT",
   "version": "4.21.2",
   "dependencies": {
    "accepts": "~1.3.8"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/npm-package-metadata-lookup-023417c7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)