Proxy compatibility

COMPATIBLE

An HTTP/API path where the app sends OpenAI-compatible or Anthropic-compatible requests directly to CSL proxy routes.

It fits systems that already emit upstream-shaped HTTP requests and do not want to start with CslClient.

Proxy compatibility is real, but it is separate from the CslClient method surface. React Native and Electron are not part of the current official example surface.

Included today

/v1/proxy/openai/v1/chat/completions
/v1/proxy/anthropic/v1/messages
direct HTTP instead of CslClient

Verified source

Proxy examples
Example smoke

Use direct HTTP for /v1/proxy/openai/v1/chat/completions and /v1/proxy/anthropic/v1/messages when your wrapper already emits upstream-shaped requests.

Proxy compatibility is real, but it is separate from the CslClient method surface. Start with SDK Server Integration only when you intentionally want the package integration path; otherwise use the Server API default.

Callback delivery

Reference overview

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.