API reference

Memories

Agents form long-term memories about the people they talk to. Read, correct, or delete them over the API. Read endpoints need memories:read; update and delete need memories:write.

Endpoints

Method & path	Ability	Notes
`GET /api/v1/memories`	`memories:read`	`limit` only (default 50, max 100) — no offset
`GET /api/v1/memories/stats`	`memories:read`
`GET /api/v1/memories/{id}`	`memories:read`
`PUT /api/v1/memories/{id}`	`memories:write`	Update → message only
`DELETE /api/v1/memories/{id}`	`memories:write`

List memories

GET /api/v1/memories takes limit (default 50, max 100) and the filters memory_type, category, and verified (boolean).

curl "https://app.hania.ai/api/v1/memories?verified=true&limit=50" \
  -H "Authorization: Bearer $HANIA_API_KEY"

The memory object

Selected fields: id, customer_id, tenant_id, memory_scope (temporary | permanent), memory_category (semantic | episodic), memory_type, category, content, optional event_timestamp, confidence_score (0–1), optional quality_score (1–5), optional source_conversation_id, verified, last_accessed_at, access_count, optional expires_at, entities, memory_tier (working | short_term | long_term | archival), created_at, updated_at.

The underlying embedding and full-text vectors are never returned.

Update a memory

PUT /api/v1/memories/{id} accepts { "content": "…", "confidence_score": 0.0–1.0, "verified": true|false } — useful for correcting a fact or marking it verified.

Stats & delete

GET /api/v1/memories/stats summarizes the memory store. DELETE /api/v1/memories/{id} permanently removes a memory.