Skip to main content
Telara

Integrations / Requesty (direct)

Requesty (direct) logo

Requesty (direct)

Direct calls to the Requesty router's OpenAI-compatible API (base_url=https://router.requesty.ai/v1), instrumented via the OpenAI SDK wrapper — no first-party Requesty wrapper exists in telara-observability today, but because Requesty is OpenAI-compatible by design ("One API. 300+ models."), the generic OpenAI wrapper pointed at the router's base URL captures spans the same way it does for any OpenAI-compatible endpoint. pip extra: pip install telara-observability[openai] Requesty returns a `cost` field inline in the `usage` object on every non-streaming response — a cost source most routers do not expose — so cost_paths checks for it before falling back to model_price_table derivation. Requesty sits between the customer and the underlying model vendor (OpenAI, Anthropic, etc.), so cost attribution here lands on Requesty 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

Before you connect

Prerequisites

A process that uses Requesty (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 Requesty (direct) at it
Enable OpenTelemetry in Requesty (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.