Skip to navigation

Organization dependency graph

View as Markdown

Returns the organization dependency graph for a standalone overview. Transitive neighborhood is limited by undirected depth (default 3) from seeds: all agents and artifact nodes with no incoming depends_on from another artifact; pure artifact cycles without agents use one deterministic seed. Isolated nodes (no edges) are always included. Optional comma-separated types filters node kinds.

Authentication

X-API-Keystring

API key supplied via the X-API-Key header. Takes precedence over bearerApiKey when both are present. Listed only on operations that actually accept a key.

OR
AuthorizationBearer

Same organization API key supplied as a Bearer token in the Authorization header (Authorization: Bearer <key>). Compatible with OpenAI-SDK-standard clients. Accepted wherever this scheme is listed on the operation — not every endpoint; if both X-API-Key and Authorization: Bearer are present, X-API-Key wins.

OR
AuthorizationBearer

Supabase session JWT from a signed-in browser session, supplied as Authorization: Bearer <jwt>. This is what the web app sends. It shares the Authorization header with bearerApiKey; the server distinguishes them by the ela_ prefix on API keys.

Query parameters

orgSlugstringRequired
depthintegerOptional1-20Defaults to 3
typesstringOptional

Response

OK
any
OR
any