Use case · Custom bots

Give your bot
context intelligence.

LeanCTX embeds in any custom bot or agent via a versioned /v1 HTTP API with Python, TypeScript and Rust SDKs. Your bot gets compressed reads, persistent memory, a knowledge graph and governance, without building any of it. One local Rust binary, lean-ctx serve, zero cloud dependency.

The problem

What it costs you today.

01

Raw JSON goes straight into the model

Every tool response, API payload and document lands unprocessed in the prompt. You pay for noise on every single call.

02

Home-grown memory is fragile

A vector store bolted to a cron job is not a memory system. Findings vanish, sessions reset, and nobody trusts the recall.

03

Every bot rebuilds the same plumbing

Caching, deduplication, retrieval, budgets: each new bot reinvents the context stack instead of shipping its actual job.

Shipped today

The capabilities that do the work.

Everything below ships in the open-source binary today. No roadmap items, no waitlists.

Your tools LeanCTX Model
Versioned /v1 API lean-ctx serve exposes read, search, memory and shell endpoints
3 SDKs Python, TypeScript and Rust, with typed clients for every endpoint
MCP gateway bridge external MCP servers through one governed entry point
Context personas reshape the layer for coding, research, support or your own domain
Knowledge store facts, decisions and blockers persist across sessions and restarts
Quickstart

From zero to first gain.

# start the context API
$ lean-ctx serve
# install the SDK
$ pip install leanctx
# connect from your bot
$ client = LeanCtxClient("http://127.0.0.1:8080")
# compressed read via the /v1 API
$ client.call_tool_text("ctx_read", {"path": "data/report.pdf"})
FAQ

Questions teams ask before adopting.

Do I need an AI coding tool to use LeanCTX?

No. lean-ctx serve runs a versioned /v1 HTTP API on your machine. Any process (a Slack bot, a support agent, a pipeline) can use compressed reads, memory and search via the Python, TypeScript or Rust SDK.

Where does my bot’s data live?

On your machine. LeanCTX is local-first with zero telemetry: cache, knowledge store and ledger are local files. Nothing leaves unless you build something that sends it.

What does it cost to embed LeanCTX?

Nothing. Local use is free forever, enforced by a public CI gate. Paid plans only add hosted sync and team planes on top.

Take back control of your context.

Free for local use, forever. CI enforces it. One binary, ten minutes to the first measured gain.