No-code quickstart
Start with conservative defaults, no prompt sharing, and one non-sensitive completion surface.
AI agents
Sponsor visible agent moments, not agent decisions.
Add sponsored moments around task progress, checkpoints, and completion screens while keeping planning, tool calls, and autonomous decisions untouched.
The sponsored moment
Monetize the visible AI state.
Agent products need strict boundaries because the system may plan, call tools, and take actions. wavebird belongs only in visible user states.
Task progress view
Checkpoint screen
Completion summary
Next-step panel
Task result review
User-visible agent status area
Request sponsorship only when the agent reaches a visible progress, review, or completion state that the user can clearly distinguish from execution.
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
- Agent workflows often include progress and result states where the user is already reviewing what happened.
- Sponsorship can sit around the workflow without affecting task execution.
- Clear separation protects trust in autonomous systems and keeps the sponsor out of decisions.
What stays untouched
- Agent reasoning
- Planner state
- Tool inputs
- Tool outputs
- Autonomous decisions
- Execution sequence
- Hidden 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 completion summary.
- Sponsor module beside a visible progress checkpoint.
- Relevant resource after the user reviews task results.
Avoid
- Sponsor influence on tool selection.
- Ads inserted into tool calls or tool outputs.
- Sponsored next actions that look like autonomous agent recommendations.
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 only when the agent enters a user-visible progress, checkpoint, or completion UI state.
Server-side matching
Send workflow category, language, timing, and consent. Do not send hidden planning traces or tool payloads.
Client-side rendering
Render the sponsor in a separate summary or checkpoint slot, never in the action sequence itself.
Controls
Decide where sponsorship is allowed.
The app decides surfaces, formats, labels, relevance, blocked categories, fallback behavior, and when the sponsor path is disabled.
Workflow eligibility
Checkpoint-only rendering
Non-sensitive flow defaults
Format controls
Industry blocking
Relevance rules
Fallback behavior
Immediate off switch
Related surfaces
Similar visible AI moments.
Next step
Add sponsorship only where the agent is visible.
Keep planning and execution clean. Start with a completion summary or checkpoint surface.