Parse it, check it, write it back
Start with one file and one language. Inspect the edit and the checks that ran.
Read existing files
Read JSON, Markdown, HTML and office documents into a common content model. Inspect support and fidelity evidence for the format you use.
Formats →Your project's context
Bind terms and writing guidance to your project's collections. Inspect which guidance applies before you edit a help article, an API reference or a legal notice.
How it works →Edit and inspect the result
Edit content through format-aware tools and inspect the resulting file diff. Configured checks report specific issues, such as a missing placeholder or a prohibited term; a passing gate covers those checks.
Checks →Add languages when you need them
Use kapi up to draft changed content and collect work that needs review. Reuse content memory, review changes in the desktop app, and run configured gates in CI.
Go multilingual →Measured
Format support is measured rather than claimed. The format-maturity and benchmark dashboards show whether it holds, under load and per format.
See the dashboards →Open source, headless
Open source, Apache-2.0, written in Go. Format-agnostic and headless: a content layer a person or an agent can drive.
Architecture →Two ways in
neokapi is a Go framework. Use it directly as a library, or through kapi , the CLI and desktop app built on it.
Go framework
Format-aware readers and writers, a unified content model, and a streaming pipeline of composable tools; embed it directly in your own Go programs.
Go quickstart →kapi: your project tool
Edit and check the content in your project. kapi resolves the terms and writing guidance that apply to a file, through the CLI, desktop app or your AI agent.
Use kapi →kgrep, ksed, kcat: format-aware grep, sed and cat that read and rewrite the text inside office files, JSON, HTML and more.