Valistry

W&B Weave

The project's calls inside the window, newest first and a page at a time, with six named columns: id, op name, when it started and ended, whether it raised, and the usage and cost summary. Never an input, never an output.

Access

Kind
A read-only key you paste
What to give
W&B API key
Why that one
A Weights & Biases API key that can read the project. Valistry reads the calls' timing, op name and usage summary with an explicit column list that carries no input and no output.

What it attributes on its own

From the source
day · project · model as Weave priced it · calls · input, output and cached tokens · what Weave costed them at · calls that raised
Needs a rule or a trace
the provider's invoice — Weave computes a cost, it does not bill you · team, workflow and agent unless a rule maps the project · outcome — evaluations are a later slice

The addresses it calls

  • https://trace.wandb.ai

Only these. A call anywhere else is refused before it leaves, and every call is logged.

Connecting it

  1. Copy your API key. wandb.ai/authorize shows it. It carries your own read access to the entity's projects. Open ↗
  2. Name the entity and the project. Both halves of the project's URL: wandb.ai/<entity>/<project>/weave.
  3. Confirm the trace server and click Test and connect. Valistry reads the last seven days of calls, reports what it found, then fills thirty.

Weave holds a cost; the provider bills it. Connecting both Weave and a provider it traces counts the same call twice — connect one. Weave is the better of the two when you need the op and the project on the row; the provider is better when you need the invoice.