create-provider-package-with-core

To build a custom provider adapter for TypeScript workflows, you wrap provider APIs and map them to core instrumentation primitives, ensuring consistent tracing across agents, LLMs, and tools without relying on prebuilt packages.

You need to instrument a custom provider integration on core primitives when your application requires consistent telemetry and tracing for agent, LLM, or tool workflows that prebuilt adapter packages do not support.

The best way to define adapter boundaries for LLM provider tracing is to build thin provider wrappers that map external provider APIs directly to core instrumentation primitives, isolating provider-specific logic from core telemetry.

Yes, this approach handles error handling and provider-specific spans for agent instrumentation by leveraging core primitives to maintain consistent tracing and production readiness across custom provider integrations.

You can use this method to ship internal tooling or private SDKs with consistent telemetry across providers by mapping diverse provider APIs to unified core instrumentation primitives for reliable tracing.

Building custom provider adapters instead of using prebuilt packages requires you to manually manage adapter boundaries, provider-specific spans, and error handling, increasing maintenance overhead for production readiness.