Proxy compatibility

COMPATIBLE

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

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

Proxy compatibility is real, but it is separate from the WavebirdClient 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 WavebirdClient

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 WavebirdClient method surface. Use SDK Server Integration when you want package-level lifecycle control; use the Server API path when you want hosted placement and rendering defaults.

Callback delivery

Reference overview

Choose hosted defaults or package control

Back to API docs Contact the team

These pages document the package layer for teams that choose wavebird to control ad requests, decisions, rendering helpers, consent, and beacons directly. Use the API docs for hosted defaults, and use contact only when you want rollout review, enterprise coordination, or help with non-standard integration constraints. Beacon billing rules live in SDK Concepts.