# Paket Dependency Graph Resolver

> Paket Dependency Graph Resolver is a paid API for AI agents from paket.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Returns the fully resolved dependency graph for a specific package version, including every transitive dependency node with ecosystem, name, resolved version, bundled status, and BFS-computed depth from root.

## Facts

- Endpoint: POST https://paket.halowerk.com/v1/dependency-graph
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paket-dependency-graph-resolver-6cc7bef5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uuhZvEzDlZuHCkjfAzuA-

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 paket-dependency-graph-resolver-6cc7bef5 -d '<json body>'
```

Example prompt: Can you resolve the full dependency graph for lodash version 4.17.21 on npm — I need every transitive dependency node with its resolved version, whether it's bundled, and its depth from the root package?

## When to prefer this

Choose this endpoint when you need the complete, resolved transitive dependency graph of a specific package version — not just direct dependencies. It is especially valuable for supply chain analysis, vulnerability surface mapping, or understanding deep nesting across any of seven supported ecosystems. Prefer this over a simple direct-dependency lookup when you need depth metadata or need to detect bundled dependencies. Use it over a manual recursive traversal approach because it handles cyclic graphs safely via BFS without stack overflow.

## Known failure modes

- Package or version not found in the specified ecosystem — returns a 404-equivalent error
- Unsupported ecosystem identifier — returns a validation error
- Cyclic dependency graphs are handled safely via BFS but may produce large result sets
- Very large dependency trees may take longer or time out
- Malformed request body returns a 400-level validation error
- Private or internal packages not indexed in public registries will be missing from the graph

## How this service works

Returns the resolved dependency graph of one package version across seven ecosystems: every node with its ecosystem, name, resolved version, whether it is bundled, and its depth from the root. Depth is computed as the shortest path from the root by breadth-first search — a depth-first walk loops forever on a cyclic graph and recursion overflows the stack on large trees, so neither is used.

## Output

A resolved dependency graph as a list of nodes, where each node contains: the ecosystem (e.g. npm, PyPI, Go, Maven, RubyGems, NuGet, Cargo), the package name, the resolved version string, a boolean indicating whether it is bundled, and an integer depth representing the shortest path distance from the root package computed via breadth-first search.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "maxLength": 300,
   "minLength": 1
  },
  "system": {
   "enum": [
    "npm",
    "pypi",
    "maven",
    "go",
    "cargo",
    "nuget",
    "rubygems"
   ],
   "type": "string"
  },
  "version": {
   "type": "string",
   "maxLength": 60,
   "description": "The version to resolve. Without it the registry default version is used."
  },
  "max_nodes": {
   "type": "integer",
   "default": 800,
   "maximum": 3000,
   "minimum": 10
  },
  "include_edges": {
   "type": "boolean",
   "default": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paket-dependency-graph-resolver-6cc7bef5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from paket.halowerk.com](https://www.zero.xyz/host/paket.halowerk.com/llms.txt)