Documentation Index
Fetch the complete documentation index at: https://docs.uselemma.ai/llms.txt
Use this file to discover all available pages before exploring further.
New to Lemma? Lemma is an observability platform for AI agents. Every agent execution becomes a trace — a structured record of timing, inputs, outputs, LLM calls, and tool invocations — so you can understand exactly what your agent did and where it went wrong. Learn more about the concepts →
Manual setup
Set environment variables
Find your API key and project ID in Lemma project settings.
Register tracer provider startup hook
Put this in your startup instrumentation file (for example
instrumentation.ts in Next.js, or a startup tracer module in Node.js):Instrument your framework with Langfuse
Langfuse is the recommended greenfield path. Keep your framework/provider instrumentation in Langfuse, then Lemma receives those emitted spans automatically via the exporter above.
- Vercel AI SDK: Langfuse Vercel AI SDK integration
- OpenAI Agents: Langfuse OpenAI Agents integration
- Claude Agent SDK JS/TS: Langfuse Claude Agent SDK JS/TS integration
- OpenTelemetry generic: Langfuse OpenTelemetry integration
Already instrumented? Reuse it
If you already emit OpenTelemetry-compatible spans with OpenInference, Arize, Braintrust, provider SDK instrumentation, or another OTel stack, you do not need to switch to Langfuse.Keep the instrumentation you have and configure Lemma as an OTLP trace export destination. See OpenTelemetry export for setup details.
See your trace in Lemma
Open the Lemma dashboard and navigate to Traces. Your trace appears within seconds; click a trace to inspect span timing, model calls, tool spans, and metadata.
What’s next
Concepts
Understand runs, spans, threads, and how they relate.
Langfuse integration
Recommended greenfield setup and export options.
OpenTelemetry export
Add Lemma to an existing OTel pipeline.
Tracing overview
Understand setup choices and trace anatomy.
Query traces from your IDE
Use the Lemma MCP server to search and inspect traces from Cursor, Claude Desktop, or any MCP client.

