Integrations / StepFun (direct)

StepFun (direct)

TENG-2205: Direct StepFun API calls (api.stepfun.ai/v1/chat/completions, OpenAI-style request/response shape per StepFun's own docs) called from customer code. StepFun has no admin or billing API — console-only. This connector only receives data if the customer's own code emits an OTel span or log record per chat call carrying the attributes below; an uninstrumented integration reports nothing, not zero. NOT independently re-verified live in this research pass: this environment could not reach StepFun's docs (platform.stepfun.com / www.stepfun.com refused connections outright), so the base URL and OpenAI-compatibility claims above rest on prior research, not a fresh fetch. OpenRouter's catalog does corroborate StepFun as an active foundation-model lab (Step3 listed), which is the only independent confirmation obtained this pass. Because StepFun's OpenAI-style shape is plausible (unconfirmed live), a generic OpenAI SDK wrapper pointed at StepFun's base_url may be able to instrument it — but there is no telara-observability SDK wrapper for StepFun specifically, so this still requires either manual OTel spans or a customer-supplied OpenAI-compatible wrapper. IMPORTANT — StepFun meters usage in platform CREDITS (~7,000,000 credits ≈ $1 per prior research), not USD. cost_derivation below resolves to a credit figure via a StepFun-specific price table, NOT a dollar amount; currency is intentionally left unset rather than USD so a raw credit count is never mislabeled as a dollar cost. Do not read the `spend` block's derived value as USD without an explicit credits-to-USD conversion applied downstream.

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 StepFun (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 StepFun (direct) at it

Enable OpenTelemetry in StepFun (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.