# mysql2 npm Dependency Diff

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

## Facts

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

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 mysql2-npm-dependency-diff-10f88307 -d '<json body>'
```

Example prompt: Can you show me what dependencies changed between mysql2 version 3.9.0 and 3.11.0 so I can assess the upgrade risk?

## When to prefer this

Use this endpoint when you need structured, machine-readable dependency diff data for the mysql2 npm package specifically, particularly for upgrade planning, security auditing, or changelog generation. Prefer it over manually scraping changelog files or npm registry pages when you need programmatic access to what changed between releases.

## Known failure modes

- Unknown or non-existent package version returns an error
- Invalid semver format for version fields
- from_version newer than target version causes unexpected result
- Rate limit or payment failure (x402 protocol)
- Package registry unavailable or metadata missing for older versions

## How this service works

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

## Output

A structured list of dependency changes between the specified mysql2 versions, including added, removed, and updated direct dependencies, along with version metadata to support upgrade planning and integration decisions.

## Request schema (JSON Schema)

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