OpenAPI

Your routes already declare their shape with Zod. openapiPlugin turns that into a live OpenAPI 3.0 document — no second source of truth, no annotations.

import { openapiPlugin } from '@machize/fastify'

openapiPlugin({
  info: { title: 'Acme API', version: '1.0.0', description: 'The Acme public API' },
})
// serves GET /openapi.json

The document is generated from the app's registered routes and their body / query / params / response schemas. Route meta: { auth: true } becomes a bearerAuth security requirement automatically.

Rendering a UI

/openapi.json is a standard document — point any viewer at it. A tiny self-contained Swagger UI route:

route({
  method: 'GET',
  url: '/docs',
  async handler({ reply }) {
    void reply.header('content-type', 'text/html')
    return `<!doctype html><html><head>
      <link rel="stylesheet" href="https://unpkg.com/swagger-ui-dist/swagger-ui.css">
    </head><body><div id="ui"></div>
      <script src="https://unpkg.com/swagger-ui-dist/swagger-ui-bundle.js"></script>
      <script>SwaggerUIBundle({ url: '/openapi.json', dom_id: '#ui' })</script>
    </body></html>`
  },
})

Generating without serving

generateOpenApi(routes, info) is a pure function — use it to write the spec to a file in CI, or feed it to a client-SDK generator.

import { generateOpenApi } from '@machize/fastify'
import { writeFileSync } from 'node:fs'

writeFileSync('openapi.json', JSON.stringify(generateOpenApi(routes, info), null, 2))

The bundled zodToJsonSchema() covers the common Zod subset (objects, strings with formats, numbers, enums, arrays, unions, optionals/defaults). Unknown types degrade to {} rather than throwing, so documentation never breaks a boot.

OpenAPI ​

Rendering a UI ​

Generating without serving ​

OpenAPI

Rendering a UI

Generating without serving