Octo: the orchestration and generative commerce layer
Octo is the AI interface inside BCC that orchestrates your network: it answers questions about your data, takes actions across products on your instruction, and resolves commerce intent in the player to your catalog, a partner's, or a retail assistant. Reading time about 6 minutes.
Three jobs
- Ask – "Which placements lost watch time this week and why?" Octo answers from your reports, along the grid, with the chart and the rows.
- Act – "Create a Paid Partner package for the running group for next month and list it." Octo drafts the package, shows it, and executes on your approval (or within Canvas guardrails, Canvas: run your network with growth and monetization agents).
- Resolve – at serve time, Octo turns a tagged moment or a viewer's question into a commerce outcome: your product, a partner's, or a routed intent to a retail assistant or marketplace (see Dynamic in-video linkouts and affiliate commerce).
Where Octo appears
- The Octo panel in BCC (every screen).
- Inside the player as the assistant behind Live & Q&A answers and shoppable prompts.
- As the Network Sales Agent that answers AdCP calls (see AdCP: make your inventory discoverable to AI buyer agents).
- Through the Intelligence SDK (see Intelligence SDK: bring Genuin signals into your own stack) for your own applications.
Guardrails
Octo acts only with the permissions of the role using it (see Invite your team and assign roles), never outside the brand safety profile (see Set moderation, roles, and brand safety), and logs every action under Settings → Audit. Data use follows your agreement and the privacy controls in Privacy and VPPA: the two-channel data flow.
Generative player direction
Octo's player components can be called as tools by large language model applications and rendered inline, so a brand's video, product, and community can appear inside AI assistants under the same rules as onsite; ask your CSM about early access.
How it runs
These reports are reviewed on a cadence and the three recommended changes are brought to you; the ones you approve are applied. Any question about the numbers can be asked in plain language from the report.
Support. Help is available 24/7 from Brand Control Center and from every page of these docs. Ask in plain language; when a person is needed, an account manager, developer, or Ops engineer joins the same thread and stays on it until it is resolved. Every Business Account owner has this on every plan (see 24/7 Octo-enabled support: how Octo brings in account managers, developers, and Ops).
API & SDK
Access: the calls in the table are the proposed Business Account API (see Business Account API: provisioning, OAuth, and the resource map), authenticated with a key scoped to the account and a role or an OAuth client acting for it; every confirmation in this article becomes a proposal you can approve by API (POST /proposals/{proposalId}:approve). Live today, the server API under /api/thirdparty authenticates with a gn-access-token (see Generate an access token), and Live API today and the Business Account API roadmap maps what is live to what is proposed.
| Call | Purpose |
|---|---|
| POST /octo/ask | Ask a question about the account in plain language; answers with the article and the setting |
| POST /octo/act | Ask for a change; returns a proposal to approve |
| POST /octo/resolve | Generative commerce routing: resolve intent at serve time to a catalog, partner, or assistant surface |
| POST /proposals/{proposalId}:approve | Approve, edit, or decline a proposal (the confirmation step in every article) |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.octo.ask(brandId, 'which feeds should I create first?');
await genuin.octo.act(brandId, 'add a keyword feed for heart health');
await genuin.octo.resolve({ placementId, intent });Live today: configured in BCC; the API for it is proposed (see Live API today and the Business Account API roadmap).
SDKs: Web SDK 2.0.6 (see Embed the Genuin Web SDK on your website), iOS SDK 2.1.5 (see Integrate the Genuin iOS SDK), Android SDK 2.1.5 (see Integrate the Genuin Android SDK), React Native 3.0.3 (see Integrate the Genuin SDK with React Native apps), and Flutter (see Integrate the Genuin SDK with Flutter apps) render Genuin and sign members in; the Node (@genuin/sdk) and Python (genuin) server SDKs are proposed with Business Account API: provisioning, OAuth, and the resource map.
