# Dependency Upgrade Plan (Multi-Package)

> Dependency Upgrade Plan (Multi-Package) is a paid API for AI agents from upgrade-brief.shopttyass-85f.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-28).

Generates a consolidated upgrade plan for up to 5 npm or PyPI packages, including breaking changes, major bumps, engine/peer dependency changes, migration guides, risk scores ordered by risk, and cross-package peer requirements.

## Facts

- Endpoint: POST https://upgrade-brief.shopttyass-85f.workers.dev/mcp?utm_source=zero.xyz#dependency_upgrade_plan
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dependency-upgrade-plan-multi-package-e8228052
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fIjffVwvWxJ4gTZomxVvh

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 dependency-upgrade-plan-multi-package-e8228052 -d '<json body>'
```

Example prompt: Can you give me a full upgrade plan for react (17 to 18), react-dom (17 to 18), and next (12 to 13) — I want to see breaking changes, migration guides, and which one is riskiest to upgrade first?

## When to prefer this

Use this endpoint when you need to plan upgrades for multiple npm or PyPI packages in a single call and want a unified risk-ranked view with cross-package peer dependency analysis. Prefer it over single-package endpoints when coordinating a batch upgrade across a project's dependency tree, especially when inter-package compatibility matters. It is the right choice when you need migration guides and risk scores aggregated and ordered, not just raw changelogs.

## Known failure modes

- Package name not found on npm or PyPI — returns an error for that package
- Version range invalid or target version does not exist — error for that package entry
- More than 5 packages submitted — request rejected or truncated
- No breaking changes documented for a package — returns empty section for that field
- Network timeout fetching registry metadata for one or more packages
- Unsupported ecosystem specified (neither npm nor PyPI)

## How this service works

Dependency upgrade plan for up to 5 npm or PyPI packages: per package the breaking changes to the target version, major bumps, engine/Python and peer dependency changes, migration guides and a risk score, ordered by risk, plus peer requirements between the listed packages.

## Output

A structured upgrade plan covering up to 5 packages: for each package, the documented breaking changes to the target version, all major version bumps in the range, engine or Python version requirement changes, peer dependency changes, a migration guide, and a numeric risk score. The packages are ordered from highest to lowest risk. Additionally, peer dependency conflicts or requirements between the listed packages themselves are surfaced.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dependency-upgrade-plan-multi-package-e8228052/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from upgrade-brief.shopttyass-85f.workers.dev](https://www.zero.xyz/host/upgrade-brief.shopttyass-85f.workers.dev/llms.txt)