Install

1. Install the SDK

npm install @klent/sdk
# or
pnpm add @klent/sdk

pip install klent-sdk

The TypeScript SDK works in Node.js ≥ 20 and any fetch-capable runtime (Deno, Bun, Cloudflare Workers). The Python SDK requires Python ≥ 3.10 and a single dependency, httpx.

Klent is delivered as a hosted product at klent.dev — there is no self-hosted distribution during alpha. Sign in at app.klent.dev; on your first sign-in Klent creates a default project for you and a ak_live_… API key. Go to Settings → API keys to view or rotate it.

VPC / on-prem. Planned as a paid Enterprise tier post-alpha. Until then, the hosted control plane on klent.dev is the only supported deployment. Reach out via [email protected] if you have a hard requirement.

3. Store the key

Keep the key out of source control. A typical setup:

# .env (gitignored)
KLENT_API_KEY=ak_live_…
KLENT_BASE_URL=https://api.klent.dev/v1  # optional, this is the default

4. Verify the key

import { KlentClient } from '@klent/sdk';

const klent = new KlentClient({ apiKey: process.env.KLENT_API_KEY! });

const execution = await klent.startExecution({ agent_id: 'sanity-check' });
console.log('✓ got execution', execution.id);

from klent_sdk import KlentClient

klent = KlentClient(api_key=os.environ["KLENT_API_KEY"])
execution = klent.start_execution({"agent_id": "sanity-check"})
print("✓ got execution", execution["id"])

If this prints an execution ID, you are ready for the quickstart.

5. Verify the package is signed (optional)

Every Klent SDK release ships with a cryptographic attestation tying the tarball you installed to the exact public source commit and CI workflow run that produced it. Worth running once if you are auditing your supply chain.

npm packages from version @klent/[email protected] and @klent/[email protected] onward include npm provenance attestations generated via Sigstore. Verify any installed @klent/* package with:

npm audit signatures

A green check confirms the tarball:

was published from klentlabs/klent-sdk-ts (public, Apache-2.0),
came from a specific publish-sdk-ts.yml (or publish-mcp-server.yml) workflow run,
has not been mutated since publish.

The "Provenance" badge on each version's page at npmjs.com/package/@klent/sdk links to the same attestation in a human-readable form.

PyPI releases from klent-sdk==0.0.2a0 onward ship PEP 740 attestations generated via Sigstore. The attestations are visible on each release file at pypi.org/project/klent-sdk/#files (click the file name → "Sigstore" link). For programmatic verification:

pip install pypi-attestations
python -m pypi_attestations verify pypi --repository \
  https://github.com/klentlabs/klent-sdk-python klent_sdk-0.0.2a0-py3-none-any.whl

A successful run confirms the wheel was built from klentlabs/klent-sdk-python (public, Apache-2.0) by a tagged publish-sdk-python.yml workflow run.

Where the SDK source lives

The SDKs and starter material are open-source (Apache-2.0) in dedicated public GitHub repositories. The hosted control plane (API, dashboard, policy engine) stays in a separate private repository.

Repo	Contains
`klentlabs/klent-sdk-ts`	`@klent/sdk`, `@klent/schema`, `@klent/mcp-server`, example agents, starter policy packs
`klentlabs/klent-sdk-python`	`klent-sdk` (PyPI)

File SDK bugs, feature requests, or PRs against those repos directly. Product-side issues (API, dashboard, billing) go to [email protected].