Developer FAQ
The answers below stay close to the released SDK surface and the documented evidence behind it.
Is this production-ready today-
Yes. @csl/wrapper-sdk is production-ready, tested and verified, and pre-pilot validated. The package surface is frozen, and the remaining step before general availability is the first live SSP partner connection.
Which integration path should I start with-
Start with Node direct plus the integration flow. The recommended first path is the direct flow built around CslClient.
Does the SDK run in Node or in the browser-
Both. Use @csl/wrapper-sdk in Node/server code and @csl/wrapper-sdk/browser in browser code.
What data do I pass into `createJob()`-
The documented minimum fields are job_type, model_id, locale, consent, prompt, and slots_requested, plus optional latency hints, client identifiers, routing hints, and callback settings.
Do I need callback verification logic myself today-
If you use the callback path, verification is handled in integration code today. A dedicated public SDK helper is not documented.
Are proxy-compatible routes part of `CslClient`-
No. Proxy compatibility is a direct HTTP integration pattern for OpenAI-compatible and Anthropic-compatible request shapes. It is not part of the CslClient method family.
How do errors surface-
Public methods stay fail-silent. Use options.onError to observe structured CslSdkError values and inspect machine-readable CslSdkErrorCode values.
Ask about integration
Start with Node direct for the recommended production-ready integration path.