Integrations / Plandex
Plandex
Plandex — spend via gateway-wrapped / instrumented model calls → OTLP.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
This connector does not take a vendor key in Settings → Integrations. Run `telara otlp` (or point the vendor’s OpenTelemetry exporter at the endpoint that command prints) so usage arrives as telemetry.
Telara has not published the exact form fields for this method yet. Complete whatever the Connect dialog shows.
Spend
What gets measured
Resolution: Per request.
Attribution: Matched to people by email.
How far back vendor history goes is not published uniformly for this connector.
- input_tokenstokens
- output_tokenstokens
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
This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.
Honesty