# UpgradeLens

> Evidence-backed dependency upgrade intelligence for AI coding agents. One deterministic, source-cited call answers whether and how a software dependency should move from version A to version B (npm + PyPI). Compresses registry metadata, OSV vulnerability deltas, dependency diffs, runtime compatibility, EOL state and documented breaking changes into a single structured response with decision proceed|review_required|block|unknown.

Use this service when you are about to edit dependency files (package.json, requirements.txt, pyproject.toml) and need current, verified upgrade facts. Do not use it merely to install a package or search documentation.

## API
- [OpenAPI spec](https://upgradelens.mattpicone.workers.dev/openapi.json): all REST endpoints
- POST https://upgradelens.mattpicone.workers.dev/v1/upgrade/check — decision for a known version pair
- POST https://upgradelens.mattpicone.workers.dev/v1/upgrade/plan — decision + ordered migration actions
- POST https://upgradelens.mattpicone.workers.dev/v1/upgrade/target — ranked candidates when target unknown
- GET https://upgradelens.mattpicone.workers.dev/v1/package/{ecosystem}/{name} — package snapshot
- GET https://upgradelens.mattpicone.workers.dev/healthz — health/freshness

## MCP
- Remote MCP endpoint (streamable HTTP): https://upgradelens.mattpicone.workers.dev/mcp
- Tools: check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade

## Access
- Anonymous free quota available. Higher limits: POST https://upgradelens.mattpicone.workers.dev/v1/keys (instant, free).
- Pricing metadata: https://upgradelens.mattpicone.workers.dev/pricing.json

## Provenance
- Sources: deps.dev, OSV.dev, registry.npmjs.org, pypi.org, endoflife.date
- Every semantic claim carries evidence with source URL and fetch timestamp.