CENDOR

Production plumbing for LLM applications.
Governance, cost, context, and testing for the layer beneath your agent — framework-agnostic, local-first, Apache-2.0.

cendor.ai · Docs · Cookbook

Cendor is two doors into one stack, sharing the flat cendor.* (PyPI) / @cendor/* (npm) import namespace — start with the libraries beneath your framework, or start governed with the SDK. Available in Python and TypeScript.

Seven small, composable libraries that plug in beneath LangChain, LlamaIndex, or any SDK: assemble context to a budget (contextkit), compress reversibly (squeeze), cap and attribute spend pre-flight (tokenguard), gate unsafe input or output — block/redact/flag — with a deterministic check (guardrails), record/replay whole runs offline (cassette), and keep a tamper-evident audit trail (acttrace) — all on a tiny shared core. Wrap your client once with instrument(); every tool subscribes to one event bus, none patches your client, none imports another.

pip install cendor-libs          # Python — the whole stack (or `pip install cendor-tokenguard` for one piece)
npm i @cendor/libs               # TypeScript — ESM-only, local-first

A governed, provider-agnostic agent SDK where budgets, tamper-evident audit, PII redaction, and record/replay testing are the foundation, not plugins. Ten provider paths, tools, handoff, sessions, and structured outputs — a governed agent in ~10 lines. Built on the libraries above, so you can always drop down to them with no concept rewrite.

pip install "cendor-sdk[openai,anthropic]"    # Python
npm i @cendor/sdk                             # TypeScript

Neither is required, and no library depends on either — the stack needs no server.

• cendor-mcp — a read-only MCP docs server that hands AI coding assistants Cendor's correct call-shapes instead of a plausible guess. Run it locally (npx @cendor/mcp / uvx cendor-mcp) or point your assistant at mcp.cendor.ai. About →

• Cendor Monitor — an optional, self-hosted OpenTelemetry container that shows the whole journey of a governed run, with the governance verdicts inline. One docker run, nothing leaves your infrastructure. Cendor never operates a telemetry endpoint; your own backend (Azure Monitor, CloudWatch, Datadog, any OTLP endpoint) stays the documented default.

• cendor-cookbook — copy-paste recipes that every one of them runs offline, with no API key: provider-shaped fake clients and committed cassettes, so git clone → run works on a plane. Browse →

npx @cendor/init      # make an existing repo Cendor-ready (offline; writes assistant rules, scaffolds instrument())
uvx cendor-init       # the Python twin

cendor-libs · cendor-sdk · cendor-libs-js · cendor-sdk-js · cendor-mcp · cendor-cookbook · cendor.ai

_{Apache-2.0 · local-first · offline by default. acttrace produces evidence to support compliance — not a guarantee, and not legal advice.}