Connect a Source

Honesty Ledger (Provenance Layer): This page tracks parameters and connections managed at the Server-known (Layer A) layer.

ZK Trust Boundary:

• What the server sees: Sync connection handshakes, agent identifier hashes, and network packet sizes.
• What stays on device: Cleartext local data, configuration files, and raw encryption key secrets.

Onboarding and Integration

To enable agent memory storage and retrieval, you must connect a sync source. The console provides copy-paste integration snippets tailored to your deployment architecture.

// Configure your AI assistant configuration block (Cursor / Claude Desktop)
{
  "mcpServers": {
    "sovseal": {
      "command": "npx",
      "args": ["-y", "@sovseal/mcp-server"],
      "env": {
        "SOVSEAL_PROJECT_TOKEN": "sov_proj_98c61a4f015d4f109b4328956ae779bb",
        "SOVSEAL_ENCRYPTION_KEY": "<your-64-hex-encryption-key>"
      }
    }
  }
}

import { SovsealClient } from "@sovseal/sdk";

const client = new SovsealClient({
  projectToken: "sov_proj_98c61a4f015d4f109b4328956ae779bb",
  encryptionKey: "<your-64-hex-encryption-key>" // Kept strictly local
});

// Store memory: Encrypted on-device before sync replication
await client.store_memory({
  content: "Agent preferred HSL color schemes for dark mode UI."
});

// Recall memory: Local vector search (0 RTT)
const memories = await client.recall_memory({
  query: "What color schemes does the user prefer?"
});

# Clone the sovereign core repository
git clone https://github.com/sovseal/core.git
cd core/supabase

# Deploy the zero-knowledge function to your own Supabase instance
supabase functions deploy v2-agent-state --project-ref <your-project-ref>

# Bind client to your self-hosted API url
export VITE_API_MODE=live
export VITE_API_URL=https://<your-project>.supabase.co/functions/v1/v2-agent-state

Key Configuration Parameters

1. SOVSEAL_PROJECT_TOKEN: A server-blind project identifier prefixing with sov_proj_. This token scopes replication queues.
2. SOVSEAL_ENCRYPTION_KEY: A cryptographically secure 256-bit (64-hex) key generated locally on your machine. This key never leaves the host machine and is never sent to the network.

Simulated Agent Sync Check

On the right side of the onboarding pane, you will see the Onboarding Progress stepper:

1. Load Identity Key: Generates or loads the local key vault.
2. Copy Integration Snippet: Confirms configuration command copied.
3. First Memory Synced: The dashboard runs a connection checker waiting for the first AES-encrypted state payload. Clicking Simulate Agent Sync runs an in-dashboard test that processes local compression, generates a 96-bit random IV, verifies AES-256-GCM, and replicates the blind payload hash to the edge. Once detected, the onboarding advances automatically.

Offline Reference Analogs: This documentation was written with visual and rhythm reference to platform/mem0-mcp.html.