Setup

The Lemma SDK sends trace JSON directly to the Lemma API.

1. Install

TypeScript
Python

npm install @uselemma/tracing

pip install uselemma-tracing

2. Set environment variables

Find your API key and project ID in Lemma project settings.

export LEMMA_API_KEY="lma_..."
export LEMMA_PROJECT_ID="proj_..."

The SDK sends to https://api.uselemma.ai by default. Pass baseUrl to new Lemma({ baseUrl }) only when you need a custom endpoint.

3. Create a client

TypeScript
Python

import { Lemma } from "@uselemma/tracing";

export const lemma = new Lemma();

from uselemma_tracing import Lemma

lemma = Lemma()

4. Send your first trace

TypeScript
Python

await lemma.trace(
  {
    name: "hello-agent",
    input: "What is the capital of France?",
  },
  async () => {
    return "Paris.";
  },
);

lemma.trace(
    "hello-agent",
    lambda trace: "Paris.",
    input="What is the capital of France?",
)

Open the Lemma dashboard -> Traces. Your trace appears within seconds.

Optional: stamp a release

A release is the stable identifier your deployment process assigns to the running app, such as an app version, commit SHA, or container tag. Change it with each deployment.

Option 1: Set an environment variable (recommended)

export LEMMA_RELEASE="<stable-deployment-identifier>"

Most CI systems expose the current commit SHA as an environment variable. Set LEMMA_RELEASE to that value during deployment to give each deployed code version a unique, stable identifier.

Option 2: Pass it when creating the client

TypeScript
Python

const lemma = new Lemma({
  release: "<stable-deployment-identifier>",
});

lemma = Lemma(release="<stable-deployment-identifier>")

Choose one option. If you set both, the release option overrides LEMMA_RELEASE. Framework adapters accept the same release option.

Next steps

Traces

Define one agent execution.

Generations

Capture LLM calls with model, prompt, completion, and timing.

Tool calls

Record tool arguments and results.

Trace contract

The exact shape Lemma reads.

Getting Started

Instrumentation

Integrations

Connections

1. Install

2. Set environment variables

3. Create a client

4. Send your first trace

Optional: stamp a release

Option 1: Set an environment variable (recommended)

Option 2: Pass it when creating the client

Next steps

Traces

Generations

Tool calls

Trace contract

​1. Install

​2. Set environment variables

​3. Create a client

​4. Send your first trace

​Optional: stamp a release

​Option 1: Set an environment variable (recommended)

​Option 2: Pass it when creating the client

​Next steps

Traces

Generations

Tool calls

Trace contract

1. Install

2. Set environment variables

3. Create a client

4. Send your first trace

Optional: stamp a release

Option 1: Set an environment variable (recommended)

Option 2: Pass it when creating the client

Next steps