Skip to main content
Telara

Integrations / Helicone

Helicone logo

Helicone

Helicone LLM proxy and observability — pull per-request cost, latency, and model usage from the Helicone API. Captures usage logged through the Helicone proxy without additional instrumentation.

API key
Spend
Actions

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A Helicone organization you can administer.
An org admin who can open Settings and issue keys. A proxy-only key is the wrong class.

Vendor setup

Get the credential

1
Open API Keys
Sign in to Helicone. Open Settings → API Keys (organization settings, not a single-request proxy header).
2
Create a read key
Click Create API Key. Name it for Telara. Grant read access to request history and metrics. Copy the key immediately.
3
Paste in Telara
Settings → Integrations → Helicone. Paste the key into the field Telara shows.

In Telara

Connect in Telara

API key

Helicone API key (Settings → API Keys). The key must have read access to request data. Available on all Helicone plans.

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
  • latency_ms
    ms
  • framework_runs
    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 write-only proxy key can ingest traffic and still cannot read history. That is a different Helicone surface.
This is not the Helicone spend-webhook connector. Webhook ingest is a separate Connect button.