Configure in the dashboard
Create a workspace, choose the standalone app surface, and test a generation-time placement with sandbox keys.
Standalone consumer AI apps
Add revenue around what your users create.
Place labeled ads around music and audio processing, image, video and 3D generation, app building and other creative AI workflows. Keep the ad outside the generated result and choose the moments that suit your product.
Surface rule
Ads stay in the application interface, outside generated media, project files and exports.
Visual sponsored moments stay labeled, separate, and controlled by your app.
The sponsored moment
Where ads fit around media generation.
Standalone consumer AI apps already contain visible moments where users wait for output, inspect a result, export a file, or decide what to do next.
Generation queues
Loading and waiting states
Result screens
Export, download, or share moments
Post-result actions
Use the generation state or result screen as the monetizable surface, with the sponsor unit clearly labeled and outside the generated artifact.
The product boundary
Ads stay in the application interface, outside generated media, project files and exports.
See the shared delivery flowRecommended setup
Generation queue, result screen, or post-response slot
Begin with one visual slot, one timing rule and clear disclosure. Keep sensitive product data out of the partner ad request.
Best placementGeneration queue, result screen, or post-response slot
Best formatBanner for compact flows, Native Ad for richer result pages, clip where a media surface exists
Best timingWhile generating or after the result is ready
Default signalBroad category, language, app surface
Data boundaryPrompt text optional and off by default
Recommended first testShow a sponsored moment during generation for free-tier users
Why this surface works
- Each generation or processing job has a compute cost. Advertising can contribute revenue alongside credits and subscriptions.
- When a job takes time, a labeled ad can use that existing wait. It must end or move out of the way when the result is ready.
- Result screens hold attention without requiring any change to the generated output.
- Paid or sensitive flows can be disabled through configuration.
What stays untouched
- Generated output
- Prompt text and model instructions
- User files
- User projects
- Paid workflows
- Sensitive categories
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
- A clip in the generation panel while a video or 3D model is being created.
- A silent banner during music generation or audio processing.
- A labeled card beside an image result or an app-builder preview, outside the exported asset.
Avoid
- Sponsored paragraphs inserted into generated writing.
- Ads blended into generated images, code, or voice output.
- Interruptive placements that block the user from seeing their result.
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 a placement from your backend when an eligible job starts. In the frontend, let render.js mount the ad while the job continues independently.
Server-side matching
Send app surface, broad category, language, timing, and consent state. Keep prompt text off unless explicitly configured.
Client-side rendering
Render the unit in your chosen slot. Hide it on no-fill or timeout; remove a waiting-state placement when the result is ready. Keep audio ads from interrupting audio creation or playback.
Controls
Decide where sponsorship is allowed.
Your app controls eligible surfaces, allowed formats and categories, placement timing and fallback behavior. These choices remain subject to wavebird's consent and safety checks, partner rules and required ad labeling.
App-side eligibility, including free or paid usage
Format allow-list
Sensitive category exclusions
Paid workflow opt-out
Result-screen placement
Generation-time placement
Fallback shell
Global kill switch
Related surfaces
Similar visible AI moments.
Choose the right moment in your product.
Compare a placement during generation with one around the result. Use your cost per job and observed ad revenue to assess the contribution.