Skip to main content
Telara

Integrations / Dust

Dust logo

Dust

Dust.tt workspace analytics — GET /api/v1/w/{wId}/analytics/export (tables: users, usage_metrics, active_users, agents, messages, skill_usage, tool_usage, source). Deprecated sibling: workspace-usage (remove after 2026-06-01 per OpenAPI). Spend connector for AI Platform Spend Governance.

API key
Spend

What Telara does

Capability matrix

Before you connect

Prerequisites

A Dust workspace you can administer.
Workspace admin who can issue API keys.

Vendor setup

Get the credential

1
Open API keys
In Dust, open Workspace settings → API Keys (or Build → API keys).
2
Create a key
Click Create API Key. Name it for Telara. Copy it immediately.
3
Paste in Telara
Settings → Integrations → Dust. Paste the key into the field Telara shows.

In Telara

Connect in Telara

API key

Dust API key with admin scope (OpenAPI: 403 without admin) and the workspace id (wId). Builder-only keys cannot call analytics/export.

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

Fields Telara asks for
  • API key
  • Workspace Id

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

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

  • messages
    count
  • credits
    count
  • conversations
    count
  • active_users
    count

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 builder key that cannot read workspace usage produces empty spend, not always an auth error.
This is Dust’s admin API. Instrumenting an agent with OTLP is a different connector.