Skip to main content
Memory federation lets your existing memory system remain authoritative while your agent consumes a bounded, normalized recall result. The SDK does not discover credentials, write to providers, synchronize stores, or promote retrieved content into Praxa personal memory.

Adopt Praxa without a migration

Add a source adapter around the client or store your backend already owns.
Use this pattern when you already have production memories and cannot justify a flag-day import.

Combine complementary sources

One agent can recall user facts from Mem0, long-term documents from LangGraph, and graph relationships from Zep or Graphiti.
Praxa ranks results with reciprocal-rank fusion over each source’s ordinal ranking. It never compares provider-native scores as though they shared one scale.

Preserve provenance for agent decisions

Every item keeps all exact-content source matches. Use those matches in traces, approval screens, or citations.
Treat memory text as untrusted contextual data. Do not reinterpret a memory as a system instruction or let it bypass your application’s authorization rules.

Continue through provider outages

MemoryFederation.recall() returns partial when at least one source succeeds and another times out, is unavailable, is unsupported, or errors.
This lets your product choose between a disclosed degraded response, a retry, or a fail-closed action policy. Never interpret a provider outage as proof that the subject has no memory.

Evaluate a future migration

Run old and proposed stores side by side, compare recall quality, and inspect which source contributed each result. The SDK supports evaluation, not an automated mirror or cutover. Provider writes and any eventual migration remain your responsibility.

Stage portable candidates

The hosted candidate API accepts the same portable eight-kind envelope for personal workspace keys. It can create, lexically query, export, and erase candidate records without activating them as first-party Praxa memory. Use this only as a qualification preview. Authenticated positive, wrong-scope, revoked-key, and cross-tenant production canaries remain pending. Deleting a candidate removes Praxa’s candidate content and creates a content-free receipt; it does not delete the provider-owned source record.

Memory federation tutorial

Connect each supported adapter and run isolation, outage, and provenance tests.

Hosted candidate API

Review the qualification boundary, scopes, routes, retention, and deletion semantics.
Last modified on August 14, 2026