Sign in only to claim founding access or manage payment. The limited local build never needs an account.
By continuing, you agree to the Terms of Service and acknowledge the Privacy Policy.
Please wait while we complete your sign-in.
Choose the environment you are setting up.
Your selected plan is saved.Continue without answering seven setup questions first.
Continuing does not charge you. You will review the plan and Terms before secure checkout opens, and you can answer these setup questions later.STEP 2 OF 7
STEP 3 OF 7
STEP 4 OF 7
STEP 5 OF 7
STEP 6 OF 7
Optional, but it helps us tailor your workspace.
0 / 4,000STEP 7 OF 7
Everything looks good. You can change these later in Settings.
GET STARTED
Start with local, zero-credential agent memory. Move to a self-hosted environment when you are ready for your own PostgreSQL, KMS, and policy controls.
Skip the manual setup: paste this prompt into Claude Code or Codex and your agent wires Lians into your codebase.
Integrate Lians (regulated AI memory: bitemporal recall, tamper-evident audit, crypto-shred erasure) into this project.
1. Detect the stack and install the SDK:
- Python: pip install lians-sdk (extras: [langchain] [langgraph] [crewai] [mcp] [all])
- TypeScript / Node: npm install @lians-ai/lians
- Go: go get github.com/Lians-ai/Lians/agentmem/sdk/go@v0.5.0
- Java (JVM 11+): ai.lians:lians-sdk:0.5.0 (Maven Central)
2. Configure via environment only (never hardcode secrets): read LIANS_URL and LIANS_API_KEY.
If they are unset, add both to .env.example and tell me to create a key in the Lians console
(API keys view), or self-host: git clone https://github.com/Lians-ai/Lians && docker compose up --build.
3. Wire memory into the agent loop (no agent loop in this project? skip to 4 and integrate at dev time instead):
- Write durable facts after meaningful exchanges: mem.add(agent_id, content, event_time, metadata).
- Recall context before responding: mem.recall(agent_id, query), or mem.recall_at(query, as_of=<ISO date>)
whenever the answer must reflect what was known or valid at a past point in time.
- Put structured keys in metadata (ticker / subject / metric) so supersession can close stale
versions automatically instead of letting revisions pile up.
4. If this project is an MCP host, or you are working inside one (Claude Desktop / Claude Code / Cursor /
VS Code), skip SDK plumbing and register the MCP server: command "uvx", args
["--from","lians-sdk[mcp]","lians-mcp"], env: LIANS_URL, LIANS_API_KEY, LIANS_AGENT_ID.
uvx ships with uv. If missing, install it first: https://docs.astral.sh/uv (winget/brew/curl).
5. Never delete or overwrite memory rows directly: supersession closes stale facts, and
POST /v1/erase (crypto-shred) is the supported auditable erasure path.
6. Finish with a smoke test: add a fact with yesterday's event_time, assert recall() returns it, and
assert recall_at(as_of=<a date before the write>) returns nothing. No key or server yet? Run it
serverless: pip install lians-sdk[local], then LocalLiansClient().
Docs: https://www.lians.ai/docs · SDKs: https://www.lians.ai/sdks
PLAYGROUND
Writes and recalls run against your own namespace on the live Lians engine. If that engine is unavailable, the Console reports the failure and never substitutes sample results.
DEVELOPER ACCESS
Create keys for your agents. A secret is shown once, while its name, prefix, creation time, and status remain available here.
Copy this secret now. It will not be shown again.
Create a key for a local agent, a staging environment, or your production service.
Checking Lians key management availability…
ACTIVITY
Current-month usage comes from your live Lians namespace. Detailed evidence exploration remains clearly marked until it is connected.
Use the Playground for live writes and recalls. A live receipt explorer will replace this preview when account evidence APIs are connected.
COLLABORATION
Give every agent a durable identity, explicit memory permissions, and an attributable history. Illustrative workspace preview: the sample records below stay in this browser and are not live account activity.
COLLABORATION
Shared, policy-scoped memory for teams, cases, and workflows. Illustrative workspace preview: the sample records below stay in this browser and are not live account activity.
ACTIVITY
Follow a memory from agent request through policy, storage, review, and recall. Illustrative workspace preview: these events are sample data, not a verified live audit trail.
ACTIVITY
Preview surface · not yet connected to live account data.
Use Playground recall today; entity metadata will appear here only after the live explorer API is connected.
ACTIVITY
Preview surface · not yet connected to live account data.
Use the live Playground today; source, validity, and receipt inspection will appear here after the explorer API is connected.
MEMORY GOVERNOR
Memory changes land as governed proposals, not silent overwrites. Low-confidence supersessions (including REFINES narrowings) and writes held by admission control queue here for a human decision before they shape the durable record.
Checking your namespace for flagged supersessions.
Checking for writes held by the admission policy gate.
ACTIVITY
Preview surface · not yet connected to live account data.
Graph relationships will appear here only after the live explorer API is connected.
ACTIVITY
Configuration UI preview · use the API documentation for live webhook operations.
The Console will not claim an empty account until the live webhook API is wired into this view.
ACTIVITY
Configuration UI preview · use the API documentation for live export operations.
The Console will not claim an empty account until the live export API is wired into this view.
ACCOUNT
These display preferences stay in this browser. They do not change engine-side retention or workspace policy.
ACCOUNT
Loading your plan…
Self-host with Community, or add managed memory operations and support as your workflows grow.