OriginChainDB
Database endpoints

Search GraphSAGE embeddings

Find nodes similar to a selected node using saved GraphSAGE embeddings.

GET /v1/tenants/{tenant}/graph/{schema}/graphsage/{rel}/topk

Search the learned GraphSAGE representationsSaved embeddings must exist before this request can compare nodes.
  1. Choose a query nodeSelect the relation, result limit and metric.
  2. Compare saved representationsSearch the trained GraphSAGE embeddings.
  3. Read similar node keysUse their scores within this similarity calculation.

Before you start

Use your database bearer token.

Connection setup

Train GraphSAGE embeddings with persistence before searching them. Use a node with a usable saved embedding.

Path parameters

FieldTypeRequired
tenantstringRequired
schemastringRequired
relstringRequired

Query parameters

FieldTypeRequired
querystringRequired
kintegerRequired
metricstringOptional

Headers

FieldTypeRequiredDescription
x-oc-db-userstringOptionalActing database user (role, grant and row-policy checks). Send with x-oc-db-key.
x-oc-db-keystringOptionalAPI key of the x-oc-db-user user.

Read the result

Each item contains a matched node key and score from the saved GraphSAGE embeddings. k asks for a result limit; it does not guarantee that the graph contains that many usable embeddings.

Response statuses

HTTP status reference
StatusWhat to do
200OK
400Correct the request before retrying.
401Check the credential and Authorization header.
402Check feature access or available credits.
403Check tenant access, roles and permissions.
408Reduce query work or adjust the timeout.
429Honor Retry-After when present; back off.
499The client cancelled the request.
500Check the outcome before retrying a write.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd