B

Historical Fact-Check API

2.65

Derivation Chain

Step 1 Popularization of ancient DNA research
→
Step 2 Surge in historical content production
→
Step 3 Historical content fact-checking Infrastructure

Problem

Content creators producing historical content on YouTube, blogs, and web novels (estimated 50,000+ in Korea) are rapidly growing, but lack expertise in historical fact verification. Content with inaccurate historical information leads to comment controversies and subscriber churn, and creators spend 2–4 hours per piece of content searching primary sources for pre-verification.

Solution

Vector-indexes Korean historical sources (Samguk Sagi, Annals of the Joseon Dynasty, Seungjeongwon Ilgi, etc.) and the latest academic databases, and provides a REST API that returns source references and match scores when historical statements are submitted. Also provides an embeddable widget for inserting a 'Verified' badge into content.

Target: History YouTubers and bloggers (1,000–100,000 subscribers), web novel authors, historical Education content production companies
Revenue Model: API pay-per-use: $0.075 per verification, Monthly Subscription: $29/month (500 verifications/month), Enterprise (publishers/Education Platforms): $150/month
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
2.0/5
V Validation
2.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (70%)

Tech Complexity
29.3/40
Data Availability
20.4/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (51/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
5.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

AI/ML [medium] Backend [medium] Frontend [low]
Dashboard