Integrations / CometAPI (direct)

CometAPI (direct)

Direct calls to the CometAPI router's OpenAI-compatible API (base_url=https://api.cometapi.com/v1), instrumented via the OpenAI SDK wrapper — no first-party CometAPI wrapper exists in telara-observability, but CometAPI documents itself as "OpenAI Compatible" so existing OpenAI-SDK code (and its observability wrapper) works unmodified against the router's base URL. pip extra: pip install telara-observability[openai] CometAPI aggregates 500+ models from multiple upstream providers behind one key and offers its own dashboard (spend, latency, call volume, budget alerts) but no bulk usage/billing pull API — dashboard only, same limitation as the other routers in this batch. CometAPI sits between the customer and the underlying model vendor, so cost attribution lands on CometAPI as the router, not on the origin model provider — a real chargeback limitation: the origin vendor's own admin-API pull (if connected) will not show these calls.

OTLP

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 process that uses CometAPI (direct) and can export OpenTelemetry.

Ability to run the Telara CLI where that process runs.

Vendor setup

Get the credential

Print the OTLP endpoint

Run `telara otlp`. It prints the endpoint and headers Telara expects. Do not paste a vendor API key on this connector.

Point CometAPI (direct) at it

Enable OpenTelemetry in CometAPI (direct) (or in your collector) and send traces to the endpoint that command prints.

In Telara

Connect in Telara

OTLP

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_tokens
tokens
output_tokens
tokens
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

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Nothing appears in Telara until that process actually emits telemetry.

This is not an admin-key connector. Org-level spend, if Telara offers it for this vendor, is a separate page.