Fan Vibes
IP division / licensing / brand managementIP Creator OS portal

Your IP to 100 partners, still under control

Official Creator Network

Replace emailing logo and guideline files, explaining, and reviewing with a single link. Distribute official guides, approved assets, and AI Skills by role, with an approval record.

Setup ₩990K + ₩90K–190K/month · Enterprise ₩15M–30M (hypothesis)

Concept screen · Official Creator Network

Match verified creators to campaigns and pay them out

Creator registration and verification → campaign matching → approval → payout ledger, on one screen.

Rights-holder view · this month
  • Verified creators
    8
    target 50 · example
  • Campaigns this month
    3
    target 6 · example
  • Approval rate
    67%
    target 90% · example
  • Disputes
    0
    target 0 · example
Concept mockup · not a deliverable
1. Creator roster

Filter verified creators by skill

Concept mockup · not a deliverable
2. Campaign matching

Recommend and invite creators that fit the campaign

Deadline · finals week D-7
Aether Realm finals week — 5 cheer apps
5 cheer apps · budget pool ₩1,500,000 (example)
Vibe codingMini gameClaude CodeWeb builder
Slots 0/5
Recommended matches
  1. @vibecoder_minjiNot invited
    Fit
    99
    Skill match · Past approval rate · Tooling
  2. @loop_junNot invited
    Fit
    97
    Skill match · Past approval rate · Tooling
  3. @quizsmith_haruNot invited
    Fit
    70
    Skill match · Past approval rate · Tooling
  4. @clip_taeoNot invited
    Fit
    67
    Skill match · Tooling
  5. @mini_byeolNot invited
    Fit
    58
    Skill match · Past approval rate
Concept mockup · not a deliverable
3. Approval · payout ledger

Only approved deliverables move to payout

Deliverable approval
CreatorDeliverableRule checkApproverStatus
@quizsmith_haruComeback-week quiz pack PassedRights-holder opsApproved
@pixel_dorongMerch illustration set PassedRights-holder opsApproved
@chart_yeonFinals prediction board Fix requestedRights-holder opsSubmitted
Payout ledger
ItemAmount (example)Creator / IP / PlatformStatus
Comeback-week quiz pack
@quizsmith_haru
₩450,000₩315,000 / ₩90,000 / ₩45,000
70 / 20 / 10
Paid
Merch illustration set
@pixel_dorong
₩600,000₩420,000 / ₩120,000 / ₩60,000
70 / 20 / 10
Scheduled

Docenty Pay settlement — the creator share is paid through the pay.docenty.ai rail (concept)

Concept mockup · not a deliverable
Why now

The problem

Every vendor, licensee, and agency asks the same question: can I use this?
There's no way to govern creators who use official assets inside AI tools like Claude and Codex.
Flow

How it works

  1. 01
    Register IP Pack
    Characters, world, and brand rules as an official Pack
  2. 02
    Split permissions
    Usage rights by role: internal, vendor, fan
  3. 03
    Call from AI tools
    Official assets inside the tools creators already use
  4. 04
    Approve & track
    Rule check → approval → usage history
Scope

What you receive

KPI

What we measure

Request and approval turnaroundPartner count and active rateRule violations blocked upfrontProjects using official assets

What we guarantee are operational deliverables (counts, process, review, reports); KPIs are presented as targets.

Receive · Do · Effect

What changes hands once you sign

📦
What you receive
Prepared by Docenty
  • Creator Portal (assets, guides, Skills, version alerts by role)
  • License-as-Code (media, territory, category, AI generation allowed)
  • check_license MCP (rulings inside the creation tool)
  • Per-partner usage history and approval record dashboard
✅
What you do
Minimal effort
  • Register the IP Pack (1 week, with Docenty support)
  • Invite licensees and vendors
  • Process the approval queue (target: within 2 days)
📈
Expected effect
Targets · measurable
  • Production inquiry emails 30/week → 9 (target)
  • 90% of rule violations blocked upfront (target)
  • Govern and track even work produced in AI tools

Production flow — you do only four things

Example schedule (concept)
  1. W0Kickoff (90 min)
    You provide
    Launch / event dates, brand assets, allowed and banned scope
    Docenty + fans
    Build the IP Pack, write License-as-Code, draft the campaign page
    You get
    An IP Pack with an agreed scope + campaign page
  2. W1Recruit · distribute
    You provide
    One official announcement (copy provided)
    Docenty + fans
    Recruit creators, ship the Pack and AI Skill, swap the demo skin
    You get
    Creator roster, build guide
  3. W2–3Build · review
    You provide
    Check the approval queue (twice a week, 10 min)
    Docenty + fans
    Fans and vibe coders (creators who code with AI) build; AI rule checks, change requests, gallery
    You get
    N approved fan pieces (rights consent included)
  4. W4Spread · settle
    You provide
    Feature the winners on official channels
    Docenty + fans
    Result-card spread, payments and creator payouts (Docenty Pay), measurement
    You get
    Participation · share · traffic · payment dashboard, reusable content library

Your total effort: a 90-minute kickoff, one announcement, approval checks twice a week (10 min each), one shout-out of the winners. Docenty runs the rest.

Concept scenario · IP business / licensing

A portal that turns 30 emails into one link and incidents into an approval queue

Character studio 'Poco Friends' — managing 40 licensees (Fictional character IP (stationery, food, and fashion licensees))

2 new characters + guideline v3 releaseBuyer's view
Who
Licensing manager, IP division
This quarter's goal
Halve the time spent answering production requests from 40 licensees, vendors, and agencies; block rule violations upfront
What keeps them up at night
30 'can I use this?' emails a week. Old logo versions, color changes, and cross-brand mashups cause an incident every quarter
How it's done today
  • ✕Guideline PDFs and asset ZIPs sent by email, no version control
  • ✕No control over what creators make with Claude or Midjourney
  • ✕Violations found after launch, with recall costs
Operating timeline
  1. Week 1
    Register IP Pack
    8 characters, lore, brand rules, License-as-Code (media, territory, category, whether AI generation is allowed).
  2. Week 2
    Open by role
    Separate internal, vendor, licensee, and fan permissions. Invite 40 licensees; expose assets per contract scope.
  3. Week 3
    Connect AI tools
    Call official assets from Claude/Codex via Skill and MCP. Rule check results appear inside the creation tool.
  4. Week 4
    Approve & track
    Submit work → automatic check → staff approval. Per-partner usage history and commercial-use dashboard.
What this campaign produces (example)
Tool
ToolDocenty
Poco Friends Creator Portal
Assets, guides, and Skills by role. Version alerts.
Inquiry email target -70%
Tool
ToolIP Creator OS
check_license MCP
Allowed / needs approval / prohibited rulings inside the creation tool.
Violations blocked upfront target 90%
Asset
AssetIP division
Licensee Approval Queue
Submission, review, and approval records. Checked before launch.
Approval turnaround target: within 2 days
Results dashboard (target mockup)
As of week 4
Active partners40 / 40
Production inquiry emails30 → 9 /week
Approval turnaround7 days → 2 days
Rule violations blocked upfront90%
Projects using official assets120
What we say in the meeting

“This isn't about opening your IP to fans without limits. It starts with letting the licensees and vendors you already manage use official assets in a controlled way.”

Proposed package
Setup ₩990K + ₩190K/month (hypothesis) · Enterprise ₩15M–30M

A concept scenario built from a fictional brand, buyer and schedule. Numbers are campaign targets, not achieved results or customer cases. Prices are a sales hypothesis (VAT excluded).

Get started

Official Creator Network pilot consultation

Sister products

Same engine, different packaging

See the full IP Creator Program

▶ DemoProposalRequest a demo