Recall - Exo

What this family does

Recall is where the derived state lives. GET /v1/recall/{recall_type} is a single operation with four views: identity returns the manifold position, basins and voice profile; graph returns nodes, edges and domains; insights returns pending proposals; temporal returns phases and time structure. Four of the seven named objects in this API are read from this one route. The rest of the family is drill-down and session history: one node with its chunks and neighbours, a full-text node search, the subject’s coding sessions, and a per-user identity snapshot.

Routes

Method	Path	Scope	What it does
`GET`	`/v1/identity/user/{user_id}`	`read`	Get a user identity
`GET`	`/v1/recall/graph/node/{node_id}`	`read`	Get a graph node
`GET`	`/v1/recall/graph/search`	`read`	Search graph node content
`GET`	`/v1/recall/sessions`	`read`	List coding sessions
`DELETE`	`/v1/recall/sessions/{session_id}`	`write`	Delete a coding session
`GET`	`/v1/recall/{recall_type}`	`read`	Recall cognitive state

Headers that apply here

Neither header is declared as an OpenAPI parameter, so neither appears in the generated schema tables.

X-Exo-Subject selects which subject the call acts for on the subject-aware routes above. Omit it to act as the key owner. See Subjects.

The shape of a call

Read the identity view.

curl https://api.get-exo.com/v1/recall/identity \
  -H "X-Exo-API-Key: $EXO_KEY"

import httpx

response = httpx.get(
    "https://api.get-exo.com/v1/recall/identity",
    headers={"X-Exo-API-Key": EXO_KEY},
)
identity = response.json()

const response = await fetch("https://api.get-exo.com/v1/recall/identity", {
  headers: { "X-Exo-API-Key": process.env.EXO_KEY! },
});
const identity = await response.json();

The response:

{
  "manifold": {
    "version": 3,
    "n_dimensions": 4,
    "n_basins": 3,
    "n_signals": 812,
    "silhouette_score": 0.41,
    "variance_ratios": [0.38, 0.24, 0.19, 0.11],
    "cumulative_variance": 0.92,
    "discovered_at": "2026-07-13T02:04:11Z",
    "refresh_count": 6
  },
  "voiceProfile": {
    "avgMessageLengthWords": 34.2,
    "formalityLevel": 0.31,
    "technicalDepth": 0.78,
    "evidenceCount": 214
  }
}

Traps

Empty is the correct answer for a new organization. Every recall view is produced by the background cognition cycle. Until it has run, the collections are empty. That is not an error and it is not a permissions problem. Pagination is opt-in, and only on the list-shaped views. Sending cursor or pageSize to a view that is not a list returns 400 pagination_unsupported. With neither parameter, responses keep their original un-paginated shape. An unknown recall_type is 404. The four values are identity, graph, insights and temporal.

API reference

Base URL, authentication, and the conventions every route shares.

Errors

The problem envelope and the full code catalogue.

​What this family does

​Routes

​Headers that apply here

​The shape of a call

​Traps

​Related