Integrations / Baidu ERNIE / Qianfan (direct)
Baidu ERNIE / Qianfan (direct)
TENG-2205: Direct Baidu ERNIE (Wenxin Yiyan) API calls via the Qianfan platform, called from customer code. Baidu has no admin or billing API — usage and spend are console-only, in the Qianfan console (console.bce.baidu.com/qianfan). 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. LOW CONFIDENCE, stated plainly per TENG-2205 instructions rather than guessed around: Qianfan's documentation is almost entirely Chinese-language, and every attempt to reach Baidu's docs/console domains from this environment this pass returned a connection failure (ECONNREFUSED), so neither the exact base URL nor OpenAI-compatibility could be independently verified live. OpenRouter's catalog does corroborate ERNIE 4.5 model variants exist as an active lab offering, which is the only independent confirmation obtained this pass. OpenAI-compatibility is UNCONFIRMED. Do not assume a generic OpenAI SDK wrapper works against Qianfan's endpoint without first checking Baidu's (Chinese-language) API reference directly. There is no telara-observability SDK wrapper for Baidu/Qianfan. Instrumentation must be manual: hand-written OTel spans around the qianfan SDK call site, emitting the gen_ai.* attributes below. The `spend.currency: USD` below is an ASSUMPTION, not a confirmed fact — Qianfan's console pricing may be denominated in CNY. Confirm against Baidu's live pricing page before populating baidu_ernie.model_price_table with real numbers.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
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_tokenstokens
- output_tokenstokens
- framework_runscount
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

