B

Politician Statement Fact-Check API

2.75

Derivation Chain

Step 1 Recurring politician credibility issues such as the Kim Nam-kook influence-peddling controversy
→
Step 2 Media/civic organization fact-checking demand
→
Step 3 Politician statement history search and contradiction detection API for media fact-check teams

Problem

Online news outlets and civic fact-checking organizations (1–10 people) spend 2–4 hours per case manually cross-referencing National Assembly transcripts, news articles, and social media to verify contradictions between politicians' past and present statements. Timeliness is critical for fact-check articles, but slow verification frequently causes them to miss the issue cycle.

Solution

A search engine with unified indexing of National Assembly transcripts + major news outlet articles + politician social media posts + LLM-based automatic contradiction/consistency analysis between statements + chronological statement evolution timeline visualization, delivered as an API.

Target: Fact-check teams at online news outlets (1–10 people), civic fact-checking organizations, politics-focused YouTubers/bloggers
Revenue Model: API usage-based: base fee of 39,000 KRW (~$29)/month (includes 500 queries/month) + 50 KRW (~$0.04) per excess query; Enterprise (news outlets) 199,000 KRW (~$149)/month (unlimited)
Ecosystem Role: Infrastructure
MVP Estimate: 1_month

NUMR-V Scores

N Novelty
3.0/5
U Urgency
4.0/5
M Market
2.0/5
R Realizability
2.0/5
V Validation
3.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 (57%)

Tech Complexity
24.7/40
Data Availability
20.4/25
MVP Timeline
12.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 (52/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
3.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

Backend [medium] Data Pipeline [high] Frontend [low]
Dashboard