API Spec Storage Arrives Before the API Reference Page Does
Knowledge can now store and manage your OpenAPI specs, but the rendered API reference page isn't live yet, and we want to be upfront about why.
Knowledge now has a place to upload, store, and manage your OpenAPI specs. If you've been waiting for a proper home for your API documentation inside your docs site, this is the first half of that — the half that's shipped today.
What's real right now
The API Specs area lets you bring in your OpenAPI spec files and keep them organized alongside the rest of your documentation. That part works today: your specs are stored, versioned like the rest of your content, and available to reference.
What isn't here yet, and why
What isn't live is the actual rendered reference page — the interactive, browsable API documentation view that most teams picture when they hear "API reference." We're building that on top of fumadocs-openapi, which is the same rendering foundation the rest of Knowledge's docs experience uses. Right now, that library's required React version doesn't line up with what's in this codebase, and until that mismatch is resolved, we can't safely turn the rendering piece on.
We'd rather tell you that plainly than leave the feature looking finished when it isn't, or than say "coming soon" without saying why. This isn't a mystery timeline — it's a specific, known dependency conflict, and closing it is what unblocks the rendered page.
What to do in the meantime
If you have OpenAPI specs, go ahead and bring them into Knowledge now — storing and organizing them there means nothing about your workflow has to change again once the rendered reference page ships. You just won't see a generated, interactive reference view from them yet.
We'll follow up with an announcement when the reference page itself is ready.