Skip to main content
GET
This endpoint queries entity-and-relationship triplets extracted from your ingested content. Pass id to scope to a single ingested item, or omit it to return all relations in the collection. Set type=memory to inspect a memory’s relations. Pagination handles large result sets.

Query parameters

Pagination pattern

Some additional notes

Cursor opacity. next_cursor is opaque (currently a numeric score). Don’t construct it client-side or assume meaning - pass back exactly what the server returned.
  • Collection-wide queries: Omitting id returns relations across the entire collection. This is useful for full-graph exports; pair with a small limit and paginate.
  • Knowledge vs memory: If the id belongs to a memory, set type=memory; otherwise the endpoint searches the Knowledge graph. The two graphs are completely separate.
  • Ordering: Treat data.relations[] as ranked by relevance within the response. Preserve order for display or LLM context, but do not compare ordering across unrelated queries as an absolute signal.
  • Graph completeness: Source relations only fully populate once the source’s indexing_status reaches completed. Items in graph_creation are searchable but their relations may still be in flight.
  • timestamp format differs by endpoint. On this endpoint each relation’s timestamp is an ISO-8601 string (e.g. 2026-05-12T08:14:00Z). The same relations surfaced as passthrough on Query (in graph_context) and List Documents carry timestamp as a Unix epoch float (seconds) instead. Normalize before comparing relation timestamps across endpoints.
Related Resources

Authorizations

Authorization
string
header
required

API key sent as a Bearer token: "Bearer prefix.secret"

Query Parameters

database
string
required

Database (canonical name for the tenant scope)

Example:

"acme_corp"

collection
string

Collection (canonical name for the sub-tenant scope)

Example:

"team_docs"

tenant_id
string
deprecated

Deprecated alias for database

Example:

"tenant_1234"

sub_tenant_id
string
deprecated

Deprecated alias for collection

Example:

"sub_tenant_4567"

id
string

Source ID (omit for database-wide relations)

Example:

"HydraDoc1234"

type
enum<string>

Corpus type: 'knowledge' or 'memory'

Available options:
knowledge,
memory
limit
integer
default:5000

Max relations to return

cursor
number

Pagination cursor

Response

OK

data
object
Example:
error
object

Error message, empty string on success.

Example:
meta
object
Example:
success
boolean

Whether the request succeeded.

Example:

true