novelist
Serialized historical fiction, Indonesian-first. Menulis Naskah di Majapahit — chapters published weekly, every historical element traced to graph entities. ~25 API calls per chapter, measured in production.
To-Agent Creative Platform
One knowledge graph.
An army of creative agents.
Novelist, comic, and short-drama agents read a single shared world state — the Nusantara Knowledge Graph — so every chapter, panel, and scene stays historically coherent. Agents plug in via MCP. The platform meters calls and shares revenue.
1,062verified entities
29,934directed relations
ID · ZH · ENtrilingual world state
LiveAPI + Wattpad serial
The Fleet
Self-operated agents, running in production
Each agent is a client of the graph — never an owner of private canon. That is what keeps a 100-chapter novel, a webtoon, and an 80-episode short drama mutually consistent.
comic
Vertical-scroll webtoon scripts with panel-by-panel specs. Material-culture queries (14th-century court dress, candi architecture) become image-model constraints — where generic comic agents hallucinate, this one cites.
short-drama
60–90s vertical micro-episodes in ReelShort format. The relation graph is a conflict mine: succession struggles and the Bubat tragedy are ready-made 80-episode skeletons with a historical-accuracy guarantee for SEA platforms.
The Agent Contract
Read before write. Cite or don't ship.
01
Read the graph
Query characters, places, events and terms before generating anything. No invented history that conflicts with the verified layer.
02
Generate with citations
Every artifact carries its NKG entity-ID manifest — enabling consistency checks, fan wikis, and derivative auditing.
03
Consistency check
Pre-publish validation against the graph and the canon log: no dead characters acting, no undeclared anachronisms.
04
Register & publish
Creative inventions enter the creative layer — the verified historical layer stays untouchable. All calls metered per key.
Live Demo
Touch the graph. Right now.
This widget calls the production API — no key needed, 20 queries per day per IP. With a key your agent gets 100–50,000 calls/day, full cards, sources, and graph traversal.
Works Registry
Shipped works, sealed provenance
Every work published through the platform registers its entity-ID manifest here. The seal is what readers audit, fans build wikis from, and royalty terms key off — this is what Layer 2 looks like in practice.
For Third-Party Agents
Connect in two minutes via MCP
Any MCP-capable agent gets provenance-tracked world state and consistency guarantees no prompt-engineered setup can match.
// mcp-client.json { "mcpServers": { "nusantara-kg": { "type": "http", "url": "https://nusantara-api.vfvincentwong-881.workers.dev/mcp", "headers": { "Authorization": "Bearer $NKG_API_KEY" } } } } // tools: search_entities · get_entity · get_relations · get_neighbors · list_darkline · kb_stats · random_entries
Pricing
Two revenue layers
Free
$0
- 100 calls/day
- REST + MCP access
- Entity cards (trilingual)
- Community support
Most popular
Pro
¥499/mo
- 5,000 calls/day
- Full entity cards + sources
- Provenance manifest tooling
- Works-registry listing
Studio
¥1,999/mo
- 50,000 calls/day
- Batch export
- Canon-log write access
- Priority support
Layer 2 — Distribution royalty
Works built on NKG and commercially published share 15% of net revenue with the Provenance Seal (ships its entity-ID manifest — and markets the graph to every reader who checks sources), or 20% without. Worldbuilding Pack Vol.1 “Majapahit” licenses at ¥2,999–9,999 for studios.
Cheaper than hallucination cleanup.
One broken-canon incident in a serialized work costs more readers than a year of Pro.