Autonomous Agent Onboarding

​

How Headless Self-Asserting Identity Works

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

// Zero-signup initialization
const client = new SovsealClient({
  // No API key required for free local tier; auto-generates sov_proj_<uuid>
  mode: "local"
});

1. Token Generation: sovseal generates an anonymous UUID project key prefixed with sov_proj_ (e.g. sov_proj_00000000-0000-4000-8000-000000000000).
2. Key Custody: The client derives a local Data Encryption Key (DEK) stored securely in the local environment (e.g. OS keychain or encrypted file store).
3. 0-RTT Local Memory: All memory operations (store, recall, search) run locally at 0-RTT latency.
4. Ciphertext Sync: If optional cloud replication is enabled, memories are synced as zero-knowledge ciphertext blobs — readable by no one else, including the server.

​

4-Command Terminal Bootstrap

# 1. Install the MCP server / SDK
npm install @sovseal/sdk

# 2. Run initial headless onboarding (auto-generates sov_proj_ token)
npx sovseal onboard --headless

# 3. Store a memory from your agent
npx sovseal store --content "User prefers TypeScript and Tailwind"

# 4. Recall memories in 0-RTT
npx sovseal recall --query "user styling preferences"

​

Transitioning to Paid Tiers (sov_live_)

• You can upgrade the project in the dashboard to issue a sov_live_ production API key.
• The server stores only a SHA-256 hash of the sov_live_ key, preserving the zero-knowledge security boundary.