No-code quickstart
Start with visual-only placements and sandbox keys, scoped to a companion or post-session surface.
Voice and realtime
Monetize realtime AI without interrupting the conversation.
Use visual companions, queue states, and post-session summaries to create sponsored moments around voice and realtime AI without breaking the live session.
The sponsored moment
Monetize the visible AI state.
Realtime AI cannot feel interrupted. Sponsorship should use visual companion surfaces, queue states, and post-session review by default.
Visual companion panel
Call setup or queue state
Post-call summary
Transcript review
Session recap
Non-intrusive pause state
Place sponsored moments in companion, setup, queue, or summary surfaces where they do not interrupt speech or alter live response timing.
Visual sponsored moments, not rewritten AI output.
Some AI monetization approaches insert sponsored text into model output. wavebird keeps the boundary clear with visual sponsored moments that are labeled, separate, and controlled by your app.
Patent-pending generation-time sponsorship.
wavebird introduced a system for showing sponsored moments while an AI response is being generated, turning wait time into revenue without delaying or altering the answer.
Recommended setup
Start with the smallest controlled surface.
The first test should be easy to reason about: one visual slot, one timing rule, clear disclosure, and no sensitive data in the sponsor path.
Why this surface works
- Realtime AI already has setup, waiting, and summary states where visual information can fit naturally.
- Visual companion surfaces avoid interrupting the conversation.
- Post-session review is a natural place for relevant sponsored resources.
- Consent and data boundaries are especially important in voice products, so the standard path keeps speech and transcript out.
What stays untouched
- Realtime speech
- Audio stream
- Transcript
- Speaker identity
- Live response timing
- Conversation flow
- Sensitive session context
Placement judgment
Good placements versus avoid.
The difference is whether the sponsor is clearly outside the AI output and easy for the user to understand.
Good
- Sponsored card in a visual companion panel.
- Sponsor module in a post-call summary.
- Banner during a non-blocking queue or setup state.
Avoid
- Audio ads interrupting the live conversation.
- Sponsored phrases inserted into voice responses.
- Sending transcripts into the ad path without explicit consent.
Implementation path
Server-side match, client-side render.
The product keeps orchestration and policy control. wavebird returns a placement decision, then the hosted renderer handles media and beacons.
Developer API path
Request placements only when a visual companion, setup, queue, or summary surface is available.
Server-side matching
Send session category, language, timing, and consent. Do not send realtime speech or transcript by default.
Client-side rendering
Render Native Ads or banners outside the live audio path and collapse the surface on no-fill.
Controls
Decide where sponsorship is allowed.
The app decides surfaces, formats, labels, relevance, blocked categories, fallback behavior, and when the sponsor path is disabled.
Visual-only defaults
Post-session surfaces
Queue and setup surfaces
No transcript sharing by default
Consent-gated signals
Format controls
Sensitive session opt-out
Immediate off switch
Related surfaces
Similar visible AI moments.
Next step
Start with a visual realtime surface.
Use a companion panel or post-session summary before testing any deeper realtime placement.