Content Generator API Roadmap — v1.1
The Content Generator API produces framework-grounded written content — posts, articles, book chapters — verified against a curated kernel store. Every output traces to a verified insight kernel, preventing fabrication.
Estimated availability: Q2 2027 (with engineering capacity).
What it will do
- List available kernels (KRN-### structural and PAIN-### recognition types)
- Generate content from a kernel + channel specification (async job)
- Verify all output passes a BS-prevention gate before delivery
- Support channels: LinkedIn short/medium/long, Substack, email, book chapter, and more
Kernel-first. Content cannot be generated without a verified kernel_id. This is a design invariant, not a configuration option — it's what guarantees the output is grounded rather than generic.
Planned endpoints
GET /v1/content/kernels — list available kernels
POST /v1/content/generate — generate content (async)
GET /v1/content/jobs/{id} — retrieve generation result
POST /v1/content/books — generate a full book (long-running async)
GET /v1/content/books/{id} — retrieve book generation result
The full spec is published in the API Reference.
Who this is for
Platforms that create MN-grounded content at scale — practitioner tools, coaching SaaS products, content marketing teams using the framework. If your use case involves generating framework-grounded written content (not just displaying scores), the Content Generator API is the right product.
Contact support if you have a use case that depends on this API.