leanctx.com valid

LeanCTX — the Context Gateway for AI systems

LeanCTX is the Context Gateway for AI systems. It sits between AI and the systems it reads, selects task-relevant context, applies supported controls before delivery, and records what the integration can observe. In context-only integrations, the host owns the model call. The workflow is Select → Control → Learn → Prove.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T15:05:37.643Z. Cached copy · Source on leanctx.com

# LeanCTX — the Context Gateway for AI systems

> LeanCTX is the Context Gateway for AI systems. It sits between AI and the systems it reads, selects task-relevant context, applies supported controls before delivery, and records what the integration can observe. In context-only integrations, the host owns the model call. The workflow is Select → Control → Learn → Prove.

## Product identity

- Brand: **LeanCTX**, one word. The CLI and package name is `lean-ctx`.
- Product category: **Context Gateway for AI Systems**.
- **Select**, **Control**, **Learn** and **Prove** are the gateway’s four steps.
- LeanCTX by Thinkery AG (CLI and packages: `lean-ctx`, `lean-ctx-bin`, `@thinkery/leanctx-sdk`) is not related to the `leanctx` prompt-compression packages on npm and PyPI.

## What it does

- Retrieves information relevant to a task and prepares it within a context budget.
- Applies PathJail file-access boundaries and configured content filters to supported read results; detected matches can be warned on, redacted or blocked before delivery.
- Reuses useful memory and scoped handoffs across tasks and agents, with source and policy evidence for inspection.
- Can route supported model and tool requests through configured routes, budgets and fallback rules.
- Connects to supported AI tools and can be integrated into products through the SDK and APIs.

## Scope and limits

- Controls apply only to supported calls routed through LeanCTX and depend on the active integration and policy configuration.
- Pattern-based filters can miss sensitive content or prompt injection; they do not provide complete detection.
- Local context processing does not mean local inference. The selected model and deployment determine where model requests are processed.
- Recorded usage, estimated costs and task outcomes depend on the workflow; review the measurement scope before comparing results.

## Offer boundaries

- Community Engine: open-source local context processing with supported tools. Local processing does not imply local inference; the chosen model and deployment determine where model requests run.
- Enterprise: a commercial, release-based offer for organizational controls and deployment. Confirm the supported features in the named licensed release and written agreement.
- SDK / OEM: five stable SDK primitives and six Agent Tools language contracts. Preview operations remain under the Python namespace `leanctx_sdk.preview`; production and OEM rights require a separate signed written agreement.

## LeanCTX Guided Onboarding

- English: https://leanctx.com/onboarding/
- Deutsch: https://leanctx.com/de/onboarding/
- One service combining workflow assessment, guided setup, hands-on team education, joint evaluation and handover.
- One agreed workflow in one test environment through an existing supported integration and model path.
- Deliverables: a test configuration, practical team training, written findings, workflow documentation and a recommendation for further use.
- Be
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=leanctx.com · GET /v1/domain/leanctx.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for leanctx.com:
1. POST https://agentwebmap.com/v1/sites/leanctx.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://leanctx.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/leanctx.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/leanctx.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.