Reference

React components

The current SDK public entrypoint is the Node/server client and types. Browser UI should use the Script Tag.

Component status

No React component is documented as the preferred v1 onboarding path. Use wavebird.js for browser rendering and consent UI.

Compatibility

If an older SDK-first integration used React helpers, keep that code path only where verified by local compatibility tests and plan migration to Script Tag or API-first rendering.

Types

Routes

API first, Script Tag second, SDK third

Back to API docs Contact the team

These pages are the advanced package layer for teams that intentionally choose @csl/wrapper-sdk. Primary onboarding still lives in the API docs, and browser-first installs should start with the Script Tag. Use contact only when you want rollout review, enterprise coordination, or help with non-standard integration constraints. Beacon billing rules live in SDK Concepts.