Skip to main content
Telara

Integrations / OpenRouter

OpenRouter logo

OpenRouter

OpenRouter LLM gateway — organization activity and analytics via Management API key (not an inference key). Pulls per-user / per-key / per-model usage and USD spend for AI Platform Spend Governance.

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

An OpenRouter account you can administer.

Vendor setup

Get the credential

1
Open Management Keys
In OpenRouter, go to Settings → Management Keys. This is not the default inference-keys page.
2
Create a management key
Issue a management key. Inference keys are the wrong class and will be rejected.
3
Paste in Telara
Settings → Integrations → OpenRouter.

In Telara

Connect in Telara

API key

OpenRouter Management API key from Settings → Management Keys. Regular inference keys (sk-or-v1-...) return 403 on analytics endpoints. Management keys cannot call completion endpoints.

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 user per day.

Attribution: Matched to people by the vendor user id.

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

  • input_tokens
    tokens
  • output_tokens
    tokens
  • requests
    count
  • spend_usd
    usd
  • tokens_total
    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

Inference keys cannot read analytics. That mismatch is the most common failed setup.
This is not the OpenRouter SDK (direct) telemetry connector.