# luxon npm Package Dependency Diff

> luxon npm Package 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-17).

Returns the dependency changes between two releases of the luxon npm package, supporting upgrade planning and integration auditing.

## Facts

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

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 luxon-npm-package-dependency-diff-a771ae7a -d '<json body>'
```

Example prompt: Can you show me what dependencies changed in the luxon npm package between version 2.5.0 and 3.0.0 so I can plan our upgrade?

## When to prefer this

Use this endpoint when you need precise, structured dependency-change data between specific luxon releases for upgrade planning, security auditing, or CI/CD automation. Prefer this over manual npm diff tools when you need machine-readable output in an agentic workflow.

## Known failure modes

- Invalid or non-existent version numbers return an error or empty diff
- Package name override to a non-existent package returns a not-found error
- Very new or pre-release versions may not yet be indexed in the registry
- Rate limiting or registry downtime may cause fetch failures

## How this service works

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

## Output

A structured diff of npm dependency changes between two luxon releases, including added, removed, and modified dependencies with their version ranges, drawn from npm registry metadata.

## Request schema (JSON Schema)

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