Esports / data / communityVibeOps data showroom + IP Creator OS

Fans vibe-code on approved data

Fan Data Showroom

Serve official API and community data as API, SDK, and MCP under rights-holder governance (key approval, scope, retention, attribution, commercial use). Fan- and creator-built apps are registered, approved, and attributed, and usage is visible to the rights holder.

Get a pilot proposal See the demo

Rights-holder SaaS subscription + free for creators (non-commercial) / fee on commercial approval (hypothesis)

Output → Use → Business value

Let fans build the apps they already build, where you can see them

Once fan apps register on approved data and policy, the rights holder finally sees who uses what, and how far.

① What you receive

🗂️
Catalog
6 approved data assets
Static, post-match and aggregate data + policy as code
🔌
API·SDK·MCP
Agent-ready access layer
search → check_policy → get_pack → register
✅
Approval queue
Fan app registration, approval, attribution
Non-endorsement notice and credits inserted automatically
📈
Dashboard
Usage and blocked violations
Data use per app · policy check results

→

② Where it is used

01
Finals week
30 prediction, cheer and watch-mission apps appear at once
02
Always on
Third-party questions get a policy link; disputes move from after-the-fact to pre-blocked
03
Next season
Reuse the best fan apps; only the data pack is refreshed

→

③ Business value (targets)

Visibility of fan apps
Today
found laterIn 4 weeks
30 registered, live
Violations blocked up front
Today
0%In 4 weeks
90%
Fan app usage in finals week
Today
official content onlyIn 4 weeks
60,000
Viewing conversion (participants)
Today
—In 4 weeks
+15 pts

Targets · concept example

The one-page report you get in 4 weeksDocenty · Fan Vibes

Finals-week data showroom report

Period: D-21 → finals week

30 registered fan apps · 0 policy violations · 60,000 uses

Approved data assets6

Registered / approved apps30 / 28

Policy checks412 allowed · 37 need approval · 9 blocked

App usage (finals week)60,000

Missing credits · violations0

Verdict

Third-party questions end with a policy link. Next season only needs a data pack refresh.

Targets · concept example

Concept screen · Data Showroom

Request and connect esports, game IP, entertainment and athlete IP data

Pick datasets from the catalog, state the purpose, and the rights holder approves. Only the approved scope connects via API, SDK and MCP.

Why now

The problem

Fans already build stats, prediction, and overlay apps on official APIs. Rights holders can't see who uses what, or how far.

AI coding tools are flooding the market with apps, but nobody serves rate-limit, retention, attribution, and commercial-use policy in a form an agent can read.

Flow

How it works

01
Approve assets
The rights holder decides what data and policy go public
02
Policy as code
Converted into rules an agent can read
03
Create
Fans and creators build apps via API, SDK, MCP
04
Register & track
App registration, approval, attribution, usage

Scope

What you receive

✓Approved data asset catalog (official API scope + community aggregates + IP Pack)
✓Policy as code: rate limits, key approval, retention, attribution, commercial approval, PII blocking
✓API, SDK, MCP (search_datasets, check_policy, get_dataset_pack, register_project)
✓Fan app registration, approval queue, auto-attribution, usage dashboard
✓Event-timed data packs (finals week, season patch, comeback)

KPI

What we measure

Approved assets / API callsRegistered fan apps / 30-day reuse ratePolicy violations blocked upfrontFan app usage during event weeks

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

Approved data catalog + policy as code (rate limits, retention, attribution, commercial use)
API, SDK, MCP + Ready-to-Build data packs
Fan app registration, approval queue, auto-attribution
Usage and event-week dashboard

→

✅

What you do

Minimal effort

Finalize the public data scope and policy (once)
Process the approval queue (twice a week)
Approve event-week data pack releases

→

📈

Expected effect

Targets · measurable

The fan app ecosystem becomes visible and governed (target: 90% of violations blocked upfront)
N fan apps launch together in finals, patch, and comeback weeks
Less time handling third-party app inquiries and disputes

Production flow — you do only four things

Example schedule (concept)

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
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
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)
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

W0

Kickoff (90 min)

W1

Recruit · distribute

W2–3

Build · review

W4

Spread · settle

You provide

Launch / event dates, brand assets, allowed and banned scope›

One official announcement (copy provided)›

Check the approval queue (twice a week, 10 min)›

Feature the winners on official channels

Docenty + fans execute

Build the IP Pack, write License-as-Code, draft the campaign page›

Recruit creators, ship the Pack and AI Skill, swap the demo skin›

Fans and vibe coders (creators who code with AI) build; AI rule checks, change requests, gallery›

Result-card spread, payments and creator payouts (Docenty Pay), measurement

You get

An IP Pack with an agreed scope + campaign page›

Creator roster, build guide›

N approved fan pieces (rights consent included)›

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 · Esports leagues / teams

Take the apps fans already build to 100 in finals week, on approved data

Fictional league 'Aether League' — finals week (Fictional esports league · no relation to any real league, team, or player)

Finals D-21Buyer's view

Who

Digital and fan experience lead, league operator

This quarter's goal

Fan dwell time and viewing conversion in finals week + third-party app risk management

What keeps them up at night

Fan-made stats and prediction apps already exist in numbers, but nobody knows who uses which data, or how far. Incidents are handled after the fact

How it's done today

✕Fans and third parties build stats, prediction, and overlay apps on the official API → the rights holder finds out afterward
✕Policy (rate limits, retention, attribution, commercial use) exists only as documents an agent can't read
✕Finals-week fan content is limited to what the league makes itself

Operating timeline

Week 1
Approve assets & policy
Finalize public data (schedules, aggregate stats, public profiles) and policy. Convert to License-as-Code.
Week 2
Open the showroom
Release API, SDK, MCP. Invite 30 creators. Tease the finals data pack.
Week 3
Create & register
Prediction lab, cheer battle, and viewing mission apps → register_project → approval queue → auto-attribution.
Finals week
Launch together & measure
Publish approved apps, feature on official channels. Measure app usage, viewing conversion, zero violations.

What this campaign produces (example)

Tool@theorycrafter_j

Finals Prediction Lab

Prediction quizzes on aggregate stats. Leaderboard.

Viewing conversion target +15%p

App@guild_master_s

Guild Cheer Battle

Cheer badges and per-set records.

Cheer badges 8,000

Tool

ToolDocenty

Fan Data MCP

search_datasets, check_policy, register_project.

30 registered apps, 0 violations

Results dashboard (target mockup)

As of week 4

Approved data assets6

Registered fan apps30

Finals-week app usage60,000

Policy violations blocked upfront90%

Viewing conversion (participating fans)+15%p

What we say in the meeting

“It's not about stopping fans from building apps. It's about letting them build on approved data and policy, so the rights holder can see it.”

Proposed package

League / team SaaS subscription (hypothesis) · free for non-commercial creators

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).

How a fan builds one

One line in, a submittable app 90 seconds later

Same in the web builder or in the Claude Code / Codex you already use. The agent fetches the IP Pack and rules; the fan writes one line of idea.

① Write one line
"Make a Crunch Lab member match test"
② The agent pulls the Pack and rules
Allowed assets · banned phrases · credits applied automatically
③ Preview → submit
Rule check shown as passed · one button into the approval queue

⏱ 90 s

fan-vibes.docenty.ai/build

IP PackCrunch Lab v2.1 · fan creation allowed

6 allowed · 4 banned · commerce: supporter pack only

Preview

Night Shift Researcher

Share

✓ Rules passed · credits added · ready to submit

✕ No account to create

Submit via link. Connect Docenty Pay only when payouts matter

✕ No design assets

The official Pack supplies characters, palette and prompts