# nanoid Dependency Diff

> nanoid Dependency Diff 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 nanoid npm package for integration and upgrade planning.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-nanoid-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/nanoid-dependency-diff-b049688e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zVf0NMjILIzv-cmAET2sN

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 nanoid-dependency-diff-b049688e -d '<json body>'
```

Example prompt: What dependencies changed in nanoid between version 4.0.2 and 5.0.0? I want to see what was added or removed before I upgrade.

## When to prefer this

Use this endpoint when you specifically need to inspect dependency-level changes between two nanoid releases — particularly useful before upgrading, for security audits, or for generating changelog content. It is purpose-built for nanoid but supports package overrides, making it suitable for dependency diffing across similar npm packages without writing custom npm registry queries.

## Known failure modes

- Invalid or non-existent version string returns an error or empty result
- from_version not found in registry history
- Package override to a non-existent npm package returns not found
- Rate limiting or upstream npm registry unavailability
- Malformed version strings rejected by the API

## How this service works

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

## Output

A structured report listing dependency changes between two specified nanoid releases, including added, removed, and updated package dependencies, sourced from npm registry metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "nanoid",
   "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/nanoid-dependency-diff-b049688e/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)