← KoreaAPI · verifiable K-culture data
Every record is cross-checked across independent sources — Wikidata, Wikipedia, MusicBrainz, OpenStreetMap, TMDB, and the Korea Tourism Organization (KTO) — on its bilingual name (Korean + official English). Two or more sources agreeing clears the single-source cap; three or more is “triple cross-verified”.
A strict bilingual identity check rejects a wrong match: a mismatch fails to a miss, never a wrong record. For foreign-origin titles we prefer the official Korean name (e.g. the drama Vincenzo → 빈센조, not a community mistransliteration). We never generate Korean names with an LLM — they come from sources.
A transparent 0–1 score on every record. Single-source or disagreeing sources are capped at 0.70 (honest: uncorroborated); two agreeing sources rise toward 1.0; three or more earn the triple-verified tier. The score + confidence are shown on every page and in the data.
Every record lists its exact sources with timestamps, and every page carries a ready “Cite as” line, so an answer engine can quote KoreaAPI with attribution.
Each record carries a SHA-256 content hash; the whole dataset has a reproducible dataset hash; the append-only history is hash-chained; and each build appends the chain head to a public, git-timestamped attestation log. Recompute it yourself — see /integrity.json and /integrity-log.jsonl.
Single-source records are clearly flagged (≤0.70). The underlying facts are derived from open sources; KoreaAPI’s added value is the verification, the Korean-official naming, the bilingual normalization, the proprietary demand signal, and the integrity trail. Integrity today is tamper-evidence (a public, committed head), not external notarization — a noted next step.
Call get_verified for the trust breakdown before citing; read each record’s content_hash to cache and re-verify; respect the Skill Score. Wire it in via /for-agents.