# next npm Package Dependency Diff Between Releases

> next npm Package 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-21).

Returns the dependency changes between two releases of the npm package 'next', supporting upgrade planning and integration audits.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-next-dependency-diff?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/next-npm-package-dependency-diff-between-releases-2b134bd2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fbkcC8Tv1JHL9Hb31a-HK

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 next-npm-package-dependency-diff-between-releases-2b134bd2 -d '<json body>'
```

Example prompt: Show me the dependency changes between next version 13.5.0 and 14.0.0 — I want to know what was added, removed, or updated before I upgrade.

## When to prefer this

Choose this endpoint when you need to programmatically inspect how the dependencies of the next npm package changed between two specific releases — especially useful for upgrade planning, security audits, or automated changelog generation. It directly queries npm registry metadata rather than requiring manual package.json comparison.

## Known failure modes

- Invalid or non-existent version string returns an error or empty diff
- Package name override to a non-existent package returns a not-found error
- from_version later than version may return empty or inverted diff
- Registry unavailability causes timeout or error
- Malformed version strings (e.g. non-semver) may cause parsing failures

## How this service works

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

## Output

A structured diff of dependency changes between two releases of the next npm package, including added, removed, and version-bumped dependencies, along with registry metadata useful for upgrade planning.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "next",
   "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/next-npm-package-dependency-diff-between-releases-2b134bd2/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)