Generative Player for LLM Applications
AI assistants call your own player as a tool and render it inline, so viewers there watch and shop in your experience, under your rules. Unlike a sponsored answer, the experience is yours and the outcomes report to you.
The generative player extends your Genuin player, the same one your SDKs render on your own pages and apps, into AI assistants. A large language model (LLM) application calls one of Supervised Intelligence's player components as a tool, and the assistant renders it inline. Your brand's video, products, and social experience then appear under the same rules as onsite.
Octo, Genuin's Supervised Intelligence interface in Brand Control Center (BCC), proposes this capability when it finds a fit on your sites and apps. It completes the steps under Set it up from your brand context. Nothing goes live until you approve it. It's part of Supervised Intelligence, and Supervised Intelligence: the orchestration and generative commerce layer explains where Supervised Intelligence appears and how it's governed.
When to use it
It's in early access, for brands that want their own player in AI assistants rather than a sponsored answer. You choose what appears, and your existing rules govern it.
A sponsored answer is paid space in the assistant's reply, and the assistant keeps the conversation. With the generative player, the assistant calls your player instead, so the viewer watches and shops in your experience. The engagement and outcomes come back to your reports.
It's different from AdCP: make your inventory discoverable to AI buyer agents. AdCP lets AI buyer agents discover and buy your packages. The generative player serves viewers: it renders your own experience inside the assistants they use.
| Surface | Who it serves | What appears |
|---|---|---|
| Generative player | Viewers in AI assistants | Your own player, with your video, products, and social experience |
| AdCP | AI buyer agents planning media | Your packages, as products to buy |
| Your own pages and apps | Viewers on your properties | Your placements, through the SDKs |
How it works
- An LLM application calls one of Supervised Intelligence's player components as a tool. The assistant renders the component inline.
- You decide which groups and products can render, and in which assistants.
- The same brand safety and consent rules apply as onsite. Supervised Intelligence never acts outside your brand safety profile, set in Set moderation and brand safety.
- Viewer data follows your agreement and the privacy controls in Privacy and VPPA.
- Paid content always carries a disclosure label, as Paid Partner Posts and Paid Partner Takeovers describes.
Set it up
Octo proposes the generative player with these steps already done. You review the result and confirm it.
- Ask your customer success manager (CSM) for early access.
- Define which groups and products can render. Communities and groups: structure your social experience for relevance explains how groups are organized.
- Confirm the rules. The same brand safety and consent rules apply as on your own placements.
Settings
| Setting | What it controls |
|---|---|
| Allowed content | Which groups and products can render inside assistants |
| Destinations | Which assistants can render your content |
| Disclosure | The disclosure shown with rendered content |
Brand safety and consent aren't separate settings here. They follow the profile and consent rules you already set for your own placements.
What it reports
Renders are reported by assistant, next to their engagement and outcomes. Measure engagement: watch time, lift, and cohorts explains how engagement is counted.
- Renders by assistant: how often each assistant rendered your content.
- Engagement: what viewers did with the rendered content.
- Outcomes: the clicks, purchases, and other results those renders led to.
Build on it
The same player renders on your own site today with the Web SDK. Embed the Genuin Web SDK on your website covers loading the script and your first embed. Add a Genuin placement to your website renders a placement whose videos follow each page's context. Customize the Genuin video player sets sizes, tile layouts, and the profile menu.
The feed and resolve calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
