If your application already uses Langfuse, point the Langfuse SDK at Catalyst to stream traces into the Catalyst Traces and Agents dashboards. Catalyst accepts the Langfuse ingestion and OTEL endpoints and converts traces, generations, spans, usage, costs, inputs, outputs, metadata, users, sessions, and tags into Catalyst spans.Documentation Index
Fetch the complete documentation index at: https://docs.inference.net/llms.txt
Use this file to discover all available pages before exploring further.
Configure Langfuse
Use your Catalyst API key as the Langfuse secret key. The public key is only present for Langfuse SDK compatibility; usepk-catalyst.
Python
Python
TypeScript
TypeScript
What Maps Into Catalyst
| Langfuse field | Catalyst field |
|---|---|
| Trace ID | Stable Catalyst trace ID derived from the Langfuse trace ID |
| Observation ID | Stable Catalyst span ID derived from the Langfuse observation ID |
| Trace name | agent.name, langfuse.trace.name |
| User and session | user.id, session.id |
| Generation model | llm.model_name, llm.provider when inferable |
| Usage and cost | Prompt/completion/total token columns and cost columns |
| Input and output | Span input/output and LLM message columns |
| Metadata and tags | Preserved under langfuse.* and halo.source.* attributes |
| Errors and warnings | Span status and status message |
View and Analyze
Once traces arrive, open the Catalyst dashboard and use the Traces tab to inspect individual trace trees. If your Langfuse trace names identify an agent or workflow, the Agents dashboard can group those runs and run Halo analysis over them. For the best Halo reports, keep trace names stable per agent or workflow and setuserId / sessionId when available.