Langfuse
Daily totals per model and environment: observations, input and output tokens, and the cost Langfuse holds. The metrics endpoint returns aggregates only — no trace, no prompt, no completion.
Access
- Kind
- A read-only key you paste
- What to give
- Public and secret key pair
- Why that one
- A Langfuse project's key pair. Valistry calls only the metrics endpoint, which returns totals — never a trace, never a prompt.
What it attributes on its own
- From the source
- day · model · environment · observations · input and output tokens · what Langfuse costed them at
- Needs a rule or a trace
- the provider's invoice — Langfuse computes or ingests a cost, it does not bill you · team, workflow and agent unless a rule maps the environment · outcome — scores are a later slice
The addresses it calls
- https://cloud.langfuse.com
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Open the project's API keys. Project settings → API keys. Self-hosted projects have the same page on your own host. Open ↗
- Create a key pair. The secret is shown once. Copy both halves.
- Paste both, confirm the host, click Test and connect. Valistry reads the last seven days a day at a time, reports what it found, then fills thirty.
Langfuse holds a cost; the provider bills it. Connecting both Langfuse and a provider it traces counts the same call twice — connect one. Langfuse is the better of the two when you need the environment or the prompt on the row; the provider is better when you need the invoice.