openai client: the prompt, the model, token counts, and latency. Bitfab works out the cost from the model and the token counts, or keeps the cost the response reports when it carries one. For the Responses API, see OpenAI Responses API.
Canonical signatures: TypeScript wrapOpenAIChat, wrapOpenAIEmbeddings, wrapOpenAITranscriptions · Python wrap_openai_chat, wrap_openai_embeddings, wrap_openai_transcriptions
Language Support
Under a trace root
Beneath a trace root, these calls on anopenai client are recorded with no wrapper, each as its own llm span named after the client class and method (Python’s async client adds Async, such as AsyncCompletions.create). The span attaches under the function that made the call.
detect, then classify, then an llm span named Completions.create carrying the prompt, tokens, and cost.
In TypeScript, the build transform rewrites each of these call sites in your code, so it works in bundled apps and the SDK never loads or patches openai. The client’s own return value is handed back, so .withResponse() keeps working. In Python, the SDK patches the openai resource classes when a trace() root is set up.
A client whose base URL is openrouter.ai is recorded the same way with provider "openrouter" and the cost OpenRouter reports; see OpenRouter.
exclude on the root matches the method name ("create", "parse") or the span name, and withNode() / node() on a wrapper (below) configures the one span.
Streaming
A streamed call (stream: true / stream=True, or chat.completions.stream()) is recorded as one llm span when the stream finishes, is closed, or fails, with usage read from the last chunk. What your code reads from the stream is unchanged. OpenAI sends usage on a chat stream only when the request asks for it:
transcript.text.done event. A stream returned from the trace root keeps the trace open until your code reads it. A stream your code drops without reading to the end is recorded when the runtime frees it, with the request and whatever was read but usually no usage, and its trace finishes then. Streamed calls always run for real during a replay.
A withNode() / node() placed directly on the client method records the stream on its own span instead of opening a second one. That span ends when the stream does, and the node’s finalize is not used.
Wrapping a call
Use a wrapper when you trace withwithSpan() / span() instead of a trace root. It wraps the function that sends the request and writes the prompt and usage into the span that is current when the call starts. It opens no span of its own. Beneath a trace root, a wrapper around a call that is already recorded records nothing more. onResponse / on_response receives each response after it is recorded. Wrappers never record a stream.
Chat completions
chat.completions.parse can be wrapped the same way.
Embeddings
Transcriptions
No duplicate spans
Each model call is recorded once:- A wrapper around a call the trace root already recorded adds nothing.
- A call the OpenAI Agents SDK integration is recording as a generation or response span, or the LangChain callback handler is recording as an LLM run, is not recorded a second time. This includes a call made inside your own LangChain chat model class, streamed or not. A call made alongside a LangChain run in the same trace is still recorded, except beside the first LangChain run in a TypeScript process (see Limitations).
- In TypeScript, calls made inside framework libraries in
node_modulesare never rewritten by the build transform, so only the framework’s own integration records them. In Python, the SDK patches the client classes, so a call another library makes through the client is recorded too, unless that library has a Bitfab integration recording it.
What gets captured
The context fields go in one context entry on the span. A key the response does not carry is left out. Without
costUsd, Bitfab works out the cost from model and the token counts.
Limitations
- Transcription models billed by the minute, such as
whisper-1, have no cost. Their spans carryaudioSeconds, and Bitfab prices tokens only. wrapOpenAIChatandwrapOpenAIEmbeddingsin TypeScript always reportprovider"openai". The wrapper cannot see the client’s base URL. Under a trace root, an OpenRouter client is recorded with"openrouter"; for a wrapped chat completion on OpenRouter, usewrapOpenRouter.- Calls outside any trace are not recorded. A wrapper used outside a span or trace records nothing and never starts a trace of its own.
- TypeScript automatic capture needs the build transform. Code the transform does not compile (for example a call made from a dependency) is not rewritten; wrap it instead.
- TypeScript: calls beside the first LangChain run in a process. The SDK hooks into LangChain in the background when the first Bitfab LangChain handler or
withTrace()root is created. If a LangChain run starts before that finishes, calls made inside it are still recorded once, but a call made at the same time outside it (for example inPromise.all) is not recorded while that first run is open. Later runs are not affected. - Python automatic capture needs Python 3.12+, the same as
trace()subtree capture. - Other endpoints are not recorded, including image generation, speech, moderation, and the Realtime API.