Octo operates your Brand Control Center: Octo proposes, you approve
Every step in these docs is done by Octo, Genuin's orchestration layer, and approved by you: Octo selects, generates, creates, and adds, and you review and say yes, change it, or say no. Nothing in Brand Control Center (BCC) has to be configured by hand, and nothing Octo does becomes public, paid, or sent without an approval you gave, either on the item or as a standing rule. Reading time about 6 minutes.
The operating loop
| Stage | Octo | You |
|---|---|---|
| Learn | Crawls your properties, reads your brand context, catalog, sources, and reports (see Brand Context and Website Crawler) | Add context Octo cannot see: audience, rules, partners, policies |
| Propose | Drafts the next thing the network needs: a grid, a hub, a feed, a partner edge, an agreement, a code change | Review it as a rendered result, not a form |
| Approve | Waits, or acts within the autonomy you set (see Octo Autonomy and Approvals) | Approve, edit inline, or decline; every decision teaches Octo |
| Do | Executes in BCC, in your CMS or repository where connected, and across the network | Nothing |
| Report | Brings back the result and the next proposal on a cadence (Canvas, Canvas: run your network with growth and monetization agents) | Read the digest; change the cadence |
What Octo does by step
- Step 1 Add Brand Elements. Creates the Business Account structure for your company type, extracts the brand kit from your site, finds and verifies properties and sources, proposes the team and roles (see Create your Business Account on Brand Control Center (BCC), Set your brand identity: name, logo, colors, and voice, Connect your website, app, and podcast feed, and Invite your team and assign roles).
- Step 2 Launch Media Network. Recommends the network model, builds the Hierarchical Grid from the crawl or your ad server, assigns player experiences and renders them (see Choose your network model: Owned, Extended, Commerce, or Retail, Register your placements on the Hierarchical Grid, and Pick your first player experience).
- Step 3 Publish Communities. Classifies your videos, generates the content hub, launches it, ships the embeds, syndicates to other platforms on your cadence, and distributes feeds across the network (see Upload your videos or connect your social profile, Launch your first community: your owned-and-operated space, Post to your hub, then curate and schedule to other platforms, and Distribute your feeds across 7K+ apps and sites).
- Step 4 Add Users. Sets up auto login against your real sign-in, proposes creators and Quests, drafts guidelines and the brand safety profile, runs the moderation queue, classifies and invites partners (see Bring your audience in with auto login and SSO, Invite creators, hosts, and contributors, Set moderation, roles, and brand safety, and Add brand partners and demand partners).
- Step 5 Sign Contract. Recommends the plan, drafts and routes the agreement, generates and places ads.txt and sellers.json, switches on demand in order, and then runs the network on a cadence (see Plans explained: Free, Self-serve, and Enterprise, Choose your monetization agreement, Sign your agreement and authorize sellers, and Activate monetization and see your first revenue).
What only you do
Verify your email, sign the agreement, enter payout details, and approve. Developers approve code changes Octo opens in your repository; Octo never deploys on its own.
Autonomy levels
Under Octo → Autonomy each kind of change has a level: ask every time (the default for anything public, paid, or sent), do and report (for changes you have approved before and marked as trusted, such as classifying new videos or refreshing ads.txt), and off. Approvals you give repeatedly are offered as standing rules; a rule is always one click to revoke. The audit log records every Octo action with the approval or rule that allowed it.
How Octo gets smarter
Octo starts from what it can see: your website, your public content, your account. Everything you add under Brand → Context (crawler scope, brand guidelines, audience notes, catalog, partner rules, policies, technical notes, legal paper) and every approval or edit you make narrows the gap between its first proposal and what you would have built yourself (see Brand Context and Website Crawler).
When Octo needs a person
Octo is available 24/7 in BCC and on every docs page. When a request needs a human (a contract clause, a custom player build, an incident), Octo brings the right account manager, developer, or Ops engineer into the same thread with the full context, and stays on the thread until it is resolved (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 |
|---|---|
| GET /brands/{brandId}/proposals | Pending proposals with what they change and why |
| POST /proposals/{proposalId}:approve | Approve, edit, or decline a proposal (the confirmation step in every article) |
| POST /octo/act | Ask for a change; returns a proposal to approve |
| PUT /brands/{brandId}/autonomy | Per change kind: ask every time, do and report, or off |
| POST /brands/{brandId}/context:crawl | Start or re-run the website crawler across verified properties |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.proposals.list(brandId, { status: 'pending' });
await genuin.proposals.approve(proposalId);
await genuin.octo.act(brandId, 'add a keyword feed for heart health');Live today: Environments, credentials, and test data.
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.
