Skip to main content

Relational memory & Insights

In stateful mode, uniqOS builds a structured model of each end user and their relationship with a personality. This guide covers what you can read back — the Insights surface — so you can observe and use that model in your own product.

Everything here is structured data. uniqOS does not store raw message text, so none of these endpoints return transcripts.

The psychological model​

Per end user, uniqOS maintains an inferred model — traits, communication style, recurring topics, and explicitly stated preferences.

  • GET /v1/end-users/{user_id}/model — the full structured model.
  • GET /v1/end-users/{user_id}/model/readable — a human-readable rendering of the same model, for showing a person what the system has inferred.

Consolidated relational memory​

Per relationship (an end user paired with a personality), uniqOS maintains a higher-level summary and its significant moments.

  • GET /v1/relationships — list relationships.
  • GET /v1/relationships/{id} — a single relationship.
  • GET /v1/relationships/{id}/memory — the consolidated memory for that relationship.

Interactions (operational traceability)​

Per-turn metadata — what happened on each interaction, without the message text.

  • GET /v1/interactions — list interactions, filterable by user and relationship.
  • GET /v1/interactions/{interaction_id} — one interaction's detail.
  • GET /v1/interactions/aggregates — rolled-up counts over a period.

End users​

  • GET /v1/end-users — list the end users in your account.
  • GET /v1/end-users/{user_id} — a single end user, including their relationships.

See the API Reference for the exact request and response schema of each endpoint, with an interactive console. To remove any of this data, see GDPR and data erasure.