# ramda NPM Package Dependency Diff

> ramda 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-21).

Returns the dependency changes between two releases of the ramda npm package for integration and upgrade planning.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-ramda-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/ramda-npm-package-dependency-diff-32e315d2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IdURmvMat6RxyiskkgDP7

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 ramda-npm-package-dependency-diff-32e315d2 -d '<json body>'
```

Example prompt: Can you show me what dependencies changed between ramda 0.28.0 and 0.29.0? I want to know what was added or removed before I upgrade.

## When to prefer this

Use this endpoint when you specifically need to understand how the dependency tree of the ramda npm package changed across releases — especially useful before upgrading, during security audits, or when automating dependency change tracking in CI pipelines. It handles the version comparison automatically (defaulting to the previous stable release), saving manual npm registry lookups.

## Known failure modes

- Unknown or invalid version string returns an error or empty result
- Non-existent preceding stable version may fail to auto-resolve the from_version baseline
- Rate limiting or payment failures may block the request
- Package registry metadata may lag for very recent releases

## How this service works

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

## Output

A structured diff of dependency changes between two ramda releases, including packages added, removed, or version-bumped, drawn from npm registry metadata. Useful for upgrade planning, security auditing, and understanding transitive dependency risk.

## Request schema (JSON Schema)

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