Skip to main content
GET
/
graph
/
neighbors
/
{path}
Get Node Neighbors
curl --request GET \
  --url https://api.example.com/graph/neighbors/{path}
{
  "401": {},
  "404": {},
  "neighbors": [
    {
      "path": "<string>",
      "name": "<string>",
      "edge_type": "<string>",
      "weight": 123,
      "theme": "<string>"
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/timepoint-ai/timepoint-clockchain/llms.txt

Use this file to discover all available pages before exploring further.

Endpoint

GET /graph/neighbors/{path}
Returns all nodes connected to the specified node through edges, including edge metadata such as type, weight, and theme.

Authentication

Requires service key authentication via X-Service-Key header.

Path Parameters

path
string
required
The full path of the node (without leading slash). Example: events/1945/world-war-ii-ends

Response

Returns an array of neighbor nodes with edge information.
neighbors
array
Array of connected nodes

Edge Types Explained

Example Request

curl -X GET "https://api.timepointclockchain.com/graph/neighbors/events/1945/world-war-ii-ends" \
  -H "X-Service-Key: your_service_key"

Example Response

[
  {
    "path": "/events/1945/atomic-bomb-hiroshima",
    "name": "Atomic Bombing of Hiroshima",
    "edge_type": "causes",
    "weight": 1.0,
    "theme": ""
  },
  {
    "path": "/events/1945/yalta-conference",
    "name": "Yalta Conference",
    "edge_type": "contemporaneous",
    "weight": 0.5,
    "theme": ""
  },
  {
    "path": "/events/1946/nuremberg-trials",
    "name": "Nuremberg Trials Begin",
    "edge_type": "contemporaneous",
    "weight": 0.5,
    "theme": ""
  },
  {
    "path": "/events/1939/world-war-ii-begins",
    "name": "World War II Begins",
    "edge_type": "thematic",
    "weight": 0.3,
    "theme": "war, military, global-conflict"
  }
]

Error Responses

404
error
Node not found
{
  "detail": "Node not found"
}
401
error
Missing or invalid service key
{
  "detail": "Unauthorized"
}

Notes

  • The response includes both incoming and outgoing edges
  • Edges are automatically generated based on temporal proximity, location, and thematic similarity
  • Manual causes edges must be explicitly created and represent curated relationships
  • An empty array is returned if the node has no neighbors

Build docs developers (and LLMs) love