Skip to main content
GET
Get a node's belief + edit history
Read-shaped but part of the write-management surface (it lives on the write-scoped family). A node not owned by the effective subject is 404. The chain names only neighbours the subject still owns and has not forgotten: a removed supersession edge, or one whose other endpoint was forgotten, drops out, matching GET /v1/graph/nodes/{id}. Version snapshots and the audit log are the node’s own record and are always returned.

Authorization

This route requires the graph:write scope. A key carrying memory:forget or write also qualifies. 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.

Notes

  • This read sits on the write-scoped family. It exposes the mutation record, so it requires graph:write rather than plain read.
  • The chain hides what you can no longer see. A link whose other endpoint was forgotten, or whose supersession edge was removed, drops out. Version snapshots and the audit log are the node’s own record and are always returned.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

node_id
string
required

The knowledge-graph node id.

Response

Successful Response

GET /v1/graph/nodes/{id}/history: belief chain + version log + audit.

audit
HistoryAudit · object[]
required
chain
SupersessionLink · object[]
required
nodeId
string
required
versions
HistoryVersion · object[]
required
title
string | null