Skip to content

Get Knowledge Graph

GET /knowledge-graph

The neighbourhood of one item: the typed relations the consolidation engine drew.

The engine has been writing knowledge_edge on every pass since M7 and nothing could read it. The walk is symmetric — a curator asking what is connected to a fact means connected, not “what does it point at” — while every edge reports its own recorded direction.

Both bounds are reported. truncated_at_depth and truncated_at_node_limit are the difference between “this is the neighbourhood” and “this is as much of it as fits”, and a client that cannot tell them apart draws missing knowledge as absent knowledge.

NameInTypeNotes
root_item_idquerystring (uuid)requiredthe item to explore outward from
depthqueryintegeroptionalDefault 1. min 1 max 5
edge_kindsquerypart_of | supports | contradicts | derived_from | supersedes | relates_to | answers | shares_topic[] | nulloptionalrepeat to allow several kinds
statusesqueryproposed | confirmed | rejected[] | nulloptionaldefault: confirmed and proposed; rejected is a tombstone
viewer_agent_idquerystring (uuid) | nulloptionalread as this agent: unlocks its private bases
knowledge_setquerystring | nulloptionala knowledge set’s slug; the walk stays inside that base min length 1 max length 120
StatusDescriptionBody
200Successful ResponseKnowledgeGraphView
422Validation ErrorHTTPValidationError
Terminal window
curl -X GET https://your-deployment.example.com/knowledge-graph \
-H "Authorization: Bearer $COBRE_TOKEN"
FieldTypeNotes
root_item_idstring (uuid)required—
depthintegerrequired—
nodesKnowledgeGraphNode[]optional—
edgesKnowledgeGraphEdge[]optional—
truncated_at_depthbooleanoptionalDefault false.
truncated_at_node_limitbooleanoptionalDefault false.