# node-fetch Dependency Diff Between Releases

> node-fetch Dependency Diff Between Releases is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-23).

Returns the dependency changes (additions, removals, updates) between two releases of the node-fetch npm package

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-node-fetch-dependency-diff?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/node-fetch-dependency-diff-between-releases-1a884d8a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_x04kqZigVn49IsU_wJGvL

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 node-fetch-dependency-diff-between-releases-1a884d8a -d '<json body>'
```

Example prompt: Show me the dependency changes between node-fetch 2.6.9 and 3.3.2 so I can plan our upgrade and see what new or removed packages we need to account for.

## When to prefer this

Choose this endpoint when you need precise, structured dependency change data between two specific node-fetch releases for upgrade planning, security auditing, or automated changelog generation. Prefer it over manual npm registry inspection when programmatic access to the diff is required. It is purpose-built for node-fetch (though the package parameter can be overridden) and works well in CI pipelines or agent workflows that evaluate dependency risk before merging upgrades.

## Known failure modes

- Invalid or non-existent version specified — returns error or empty diff
- Package name override points to a non-existent npm package — returns 404 or error
- from_version is newer than version — may return inverted or empty diff
- Rate limiting or payment failure via x402 protocol — call blocked
- Registry metadata unavailable for old versions — partial or missing data

## How this service works

node-fetch Dependency changes between releases: Dependency changes between releases for npm package node-fetch. Inspect registry metadata for integration and upgrade planning. Package and version can be overridden.

## Output

A structured diff of npm dependencies between two node-fetch releases, listing which packages were added, removed, or had their version constraints changed, enabling developers to assess upgrade impact and integration risk.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "node-fetch",
   "maxLength": 150
  },
  "version": {
   "type": "string",
   "maxLength": 100
  },
  "from_version": {
   "type": "string",
   "maxLength": 100,
   "description": "Defaults to the preceding stable semantic version."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/node-fetch-dependency-diff-between-releases-1a884d8a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)