# npm Package Health & Supply-Chain Metadata Snapshot

> npm Package Health & Supply-Chain Metadata Snapshot is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.021/call, status down (last checked 2026-09-15).

Purchases a health and supply-chain metadata snapshot for a given npm package, returning a job ID for async result retrieval.

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_f1d0e8843dad4e5e/purchase
- Price: $0.021/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/npm-package-health-supply-chain-metadata-snapshot-1b7781b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TYLnTrFt_z5ObrCwnCh8q

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-health-supply-chain-metadata-snapshot-1b7781b0 -d '<json body>'
```

Example prompt: Can you pull a health and supply-chain metadata snapshot for the npm package 'lodash' — I want to know if it's well-maintained, safe to use, and free of known supply-chain risks?

## When to prefer this

Choose this endpoint when you need structured, AI-ready npm package health and supply-chain metadata — including maintenance signals, dependency risk, and provenance info — as a paid data product via micropayment. Prefer this over manual npm registry scraping when you need aggregated, pre-analyzed health signals in a single call, or when operating inside an x402-capable agent framework that handles USDC micropayments automatically.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment rejected — results in 402 Payment Required
- Invalid or non-existent npm package name — may return an error or empty snapshot
- Service timeout if upstream npm registry or analysis pipeline is slow
- Missing required parameters (e.g. no package name) — likely 400 Bad Request
- Rate limiting or quota exceeded — 429 Too Many Requests

## How this service works

Purchase: npm Package Health & Supply-Chain Metadata Snapshot

## Output

Returns a JSON object containing a job_id (string identifying the async job), status (current processing state), and thread_id (for tracking the request thread). The actual metadata snapshot is retrieved via a separate job-status endpoint using the job_id.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "job_id": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "thread_id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/npm-package-health-supply-chain-metadata-snapshot-1b7781b0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)