Get a graph node
Recall
Get a graph node
Drill into one knowledge-graph node: its metadata, the full text of its chunks, and up to 100 of its strongest edges with the neighbouring node labels resolved.
GET
Get a graph node
Scoped to the effective subject (the API key owner by default, or the subject named by
X-Exo-Subject). A node belonging to another subject or another org returns 404.
Authorization
This route requires theread scope.
A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
Every error is an RFC 9457
application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Path Parameters
Response
The node, its content and its strongest neighbouring edges.
Full node detail for GET /api/v1/graph/nodes/{nodeId} (Story 4-4).
Single-item response (unwrapped, ARCH-19). Includes content, metadata, connected edges with neighbor labels, domain, and projects. Reusable across dashboard click, project view, and context trace.