Skip to main content
Telara

Integrations / Gcore Everywhere Inference (direct)

Gcore Everywhere Inference (direct) logo

Gcore Everywhere Inference (direct)

Direct calls to a Gcore Everywhere Inference deployment's OpenAI-compatible API (per-deployment base_url, e.g. https://model-<deployment>-<project>-<account>.ai.gcore.dev/v1 — Gcore issues one endpoint per deployed model rather than a single shared router URL), instrumented via the OpenAI SDK wrapper. No first-party Gcore wrapper exists in telara-observability; Gcore's own docs confirm the deployed-model endpoint is queried with the Python/JS OpenAI SDK, so the generic OpenAI wrapper pointed at the deployment's base URL captures spans the same way it does for other OpenAI-compatible endpoints. pip extra: pip install telara-observability[openai] Gcore hosts open-weight models from its Application Catalog (Llama, Mistral, etc.) on Gcore-operated GPU inference nodes and bills per minute of compute time, not per token — so token-derived model_price_table cost here is a best-effort proxy, not Gcore's actual invoiced figure. Gcore sits between the customer and the underlying open-weight model, so cost attribution lands on Gcore as the inference host, not on a separate upstream model vendor (there is none to bill — the weights are open and Gcore is the only biller).

OTLP
Spend

What Telara does

Capability matrix

Before you connect

Prerequisites

A process that uses Gcore Everywhere Inference (direct) and can export OpenTelemetry.
Ability to run the Telara CLI where that process runs.

Vendor setup

Get the credential

1
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.
2
Point Gcore Everywhere Inference (direct) at it
Enable OpenTelemetry in Gcore Everywhere Inference (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.