# dayjs Dependency Diff

> dayjs 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 npm package dayjs, supporting custom version ranges for upgrade planning.

## Facts

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

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 dayjs-dependency-diff-ecc7743e -d '<json body>'
```

Example prompt: Can you show me the dependency changes between dayjs 1.10.8 and 1.11.0? I want to know what new packages were added or removed before I upgrade.

## When to prefer this

Choose this endpoint when you specifically need to inspect dependency-level changes for the dayjs npm package between releases, particularly for upgrade planning, supply chain auditing, or CI/CD automation. It is preferable over manual npm registry inspection when you need structured, programmatic output about what changed.

## Known failure modes

- Invalid or non-existent version strings return an error
- Package name override to a non-existent package fails lookup
- from_version defaults to preceding stable version if not provided; if no preceding version exists, may error
- Rate limiting or upstream npm registry unavailability may cause failures

## How this service works

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

## Output

A structured diff of dependency changes between two dayjs releases, including added, removed, and potentially modified dependencies, drawn from npm registry metadata for the specified version range.

## Request schema (JSON Schema)

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