Reference docs go stale the moment you ship. Ferndesk turns your OpenAPI spec into a precise, searchable API reference, then keeps it current as your endpoints, parameters, and responses change.
API documentation is uniquely unforgiving. Rename a field, add a required parameter, change a status code, and the reference your developers depend on is quietly wrong. They find out when an integration breaks in production.
Fern reads your OpenAPI spec and your codebase, renders an exact API reference, and updates it the moment your API changes, so your docs and your API never drift apart.
Point Ferndesk at an OpenAPI or Swagger definition, in JSON or YAML, uploaded directly or fetched from a URL. Ferndesk validates the spec, then renders every endpoint, parameter, authentication scheme, and response into a fast, searchable API reference. Already documenting your API in GitBook, Mintlify, or another tool? Ferndesk imports your existing reference, so switching never means starting over.
Ferndesk tracks the spec your API is built from and notices the moment it changes. When you ship a new endpoint, rename a field, or return a different error code, Fern understands the impact and updates the reference and the guides around it. Your API documentation follows your API, without anyone remembering to update it.
An endpoint list is not documentation. Fern reads your codebase to write the narrative docs around your API: authentication walkthroughs, quickstarts, common workflows, and error handling. The reference shows every parameter. The guides show developers how to ship.
Your API reference, developer guides, and customer help articles live together, under your own domain, fully searchable, with built-in analytics. Embed it in your product with the Ferndesk widget so developers can look up an endpoint without leaving your app.
With Ferndesk, the only help center that never goes out of date. Sign up today and ask Fern to write your first few articles.