Lians
Bitemporal long-term memory for AI agents. Keep current facts clean, reconstruct what an agent knew at a past time, and retain tamper-evident audit records.
Install
pip install lians-sdk
pip install lians-sdk[local] # SQLite plus real local semantic embeddings
pip install lians-sdk[mcp] # Local MCP server
pip install lians-sdk[langchain] # LangChain
pip install lians-sdk[langgraph] # LangGraph
pip install lians-sdk[crewai] # CrewAI
pip install lians-sdk[openai-agents] # OpenAI Agents SDK
pip install lians-sdk[autogen] # AutoGen v0.4
pip install lians-sdk[all] # Everything
Quickstart
from datetime import datetime, timezone
from lians import LocalLiansClient
mem = LocalLiansClient() # No server, Docker, or API key
mem.add(
agent_id="analyst-1",
content="NVDA FY2026 revenue guidance raised to $40B",
event_time=datetime(2025, 11, 19, 16, tzinfo=timezone.utc),
metadata={"ticker": "NVDA", "metric": "revenue_guidance"},
importance=0.9,
)
# Superseded facts are excluded before they reach the model
current = mem.recall(agent_id="analyst-1", query="NVDA revenue guidance")
# Reconstruct what was known on a past date
past = mem.recall_at(
agent_id="analyst-1",
query="NVDA revenue guidance",
as_of=datetime(2025, 3, 1, tzinfo=timezone.utc),
)
Why Lians
- Bitemporal facts with event time and ingestion time
- Deterministic supersession before memories reach the model
- Point-in-time recall and lookahead-bias checks
- Tamper-evident audit history and a crypto-erasure workflow
- Local SQLite mode with no server or API key
- Hosted and self-hosted deployment paths
See the published benchmark results, regulated-memory evaluation, and public correction ledger. The evaluation includes runnable adapters so results can be reproduced and challenged.
Framework integrations
from lians.langchain_integration import LiansChatHistory, build_tools
from lians.langgraph_integration import create_recall_node, create_remember_node
from lians.crewai_integration import build_crewai_tools
from lians.openai_agents_integration import build_openai_agent_tools
from lians.autogen_integration import build_autogen_tools
Hosted or self-hosted API
from lians import LiansClient
mem = LiansClient(base_url="https://mem.yourfirm.internal", api_key="...")
Full documentation: github.com/Lians-ai/Lians
Release files for lians-sdk 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lians_sdk-0.5.0.tar.gz | 278.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lians_sdk-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 606.3 kB
Release files / lians_sdk-0.5.0.tar.gz
| Download URL | lians_sdk-0.5.0.tar.gz |
|---|---|
| Size | 278.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed8ba6cd0ba31a30faadc68977f291de585f76ee6ebfc2fc26a1b10726b12245
|
|
BLAKE2b-256 checksum How to use checksums |
28587286ecfceb21e35266a27b6bc36038444b6d1bbc2f8b2d67dc6237111017
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 2, 2026.
Transparency logRelease files / lians_sdk-0.5.0-py3-none-any.whl
| Download URL | lians_sdk-0.5.0-py3-none-any.whl |
|---|---|
| Size | 328.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a8a2768610c1ed465179a2db3b12b793223046debd8f3b708d3efe28da90197
|
|
BLAKE2b-256 checksum How to use checksums |
5bccaae70c17311b475e2b34b2cb9ede1bf6a050029708cafd3ccc572f358b76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 2, 2026.
Transparency log