Integrations / Weights & Biases (Weave)

Weights & Biases (Weave)

W&B Weave POST /cost/query (HTTP Basic with API key). Authority: apis.io wandb.

API key

Spend

What Telara does

Capability matrix

Indexes No Tracks spend Yes Discovers shadow AI No Runs actions No Real-time events No

Before you connect

Prerequisites

A Weights & Biases organization with Weave (or the W&B API) you can administer.

A user who can open user settings and copy an API key.

Vendor setup

Get the credential

Open API keys

Copy the key

Copy the API key. W&B sends it as HTTP Basic — Telara’s form handles that. Prefer a service account key if your org has them.

Paste in Telara

Settings → Integrations → Weights & Biases (Weave). Paste the API key. Enter entity/project if the form asks.

In Telara

Connect in Telara

API key

W&B API key used as HTTP Basic credentials.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

API key

Spend

What gets measured

Resolution: Per run.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

input_tokens
tokens
output_tokens
tokens

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

A key from a personal entity will not see the company entity’s Weave traces.

This reads W&B admin/usage data. It is not an OTLP exporter from your training jobs.