What breaks if this resource changes
Walks the dependency graph from one root node and returns every dependent found (breadth-first, bounded by maxDepth/maxNodes), summarized into an impact rollup. Backs the pre-release impact card on the Prompts page and the delete-blocking check on Evaluations.
Dependency direction: an edge’s to depends on its from — walking dependents from a node answers “what would be affected if I changed this,” which is the reverse of the call direction for prompt/model edges (an agent calls a prompt or model, but the prompt or model change is what affects the agent, so the edge points prompt→agent / model→agent).
Authenticated with a dashboard session (browser cookie), not x-api-key, and requires the dashboard:read permission. There is no server-side cache in front of this endpoint today — every request rebuilds the graph, so computedAt in the response is effectively “now.”
Path Parameters
Project id.
Query Parameters
The root node id, <kind>:<key> — e.g. prompt:support-reply or evaluator:3f9c2b1a-.... Keys are names for prompt/agent/ model, UUIDs for row-backed kinds (policy, evaluator, dataset, alert). Always passed as a query parameter, never a path segment, since a key can itself contain a colon or slash.
Maximum hops from the root to traverse.
1 <= x <= 5Lookback window for observed (ClickHouse) call volume and cost.
1 <= x <= 90Maximum total dependents returned before truncating.
1 <= x <= 2000Response
The root node, its dependents, and the summarized impact.
True only when the walk hit maxDepth/maxNodes AND the graph genuinely continues beyond that point — not merely because the walk stopped exactly at the cap with nothing left beyond it.
When this response's graph was built. There is no server-side cache in front of this endpoint today, so this is effectively "now" on every request.

