Skip to main content
Device memory reuses the existing memories.create and memories.search endpoints. Pass snapshot or snapshot_ref instead of collection_id — they are mutually exclusive.
All endpoints require authentication via the Authorization: Bearer <token> header.

Export Snapshot

Export a collection’s full graph state as a portable snapshot.
To export directly to customer-owned object storage, pass a signed URL destination:

Store Memory

The existing /v1/memories endpoint accepts a snapshot or snapshot_ref field instead of collection_id. When a snapshot source is provided, Nebula processes the content statelessly and returns an updated snapshot or writes the updated snapshot to your signed URL.
Returns { "snapshot": <updated_snapshot> } when using device memory mode.
With customer-owned snapshot storage, provide a signed URL reference:

The existing /v1/memories/search endpoint accepts a snapshot or snapshot_ref field instead of collection_ids. Nebula scores your snapshot statelessly and returns results. Nothing is persisted.
Returns a graph-shaped SnapshotSearchResult: entities (each with id, name, category, description, score) and relationships (each with id, subject_id, object_id, predicate, description, weight). This is distinct from the standard MemoryResponse returned by collection-based search.
Search can also load the snapshot through a signed URL:

Import Snapshot

Import a snapshot into an ephemeral server-side collection. Useful for debugging or running server-side operations against a client-owned snapshot.
Returns { "ephemeral_collection_id": "<uuid>" }.

Customer-Owned Snapshot Objects

Use snapshot_ref when snapshots are too large to send inline or when your application stores snapshots in customer-owned object storage.
Signed URLs must use public HTTPS destinations. Nebula rejects private, loopback, and link-local hosts, does not follow redirects, and caps snapshot download size.