OpenAPI Scanner on Desktop
Generates OpenAPI 3.1 from your backend project folder: fast structural scan with optional local AI inference.
Generates an OpenAPI 3.1 file (openapi.json) from your backend project folder, without running the API or writing the spec by hand.
What the scanner does
- Explores: Locates files with HTTP routes (controllers,
routes/,handlers/,Program.cs, etc.). - Extracts: Retrieves methods, paths and DTOs/models for
components.schemas. - Generates: Creates
openapi.jsonwith an analysis summary. - Uploads: Allows uploading the file directly to a Capydox web workspace.
The default flow is structural scanning: fast, CPU-only, no AI model required.
Quick usage guide
- Open: Go to Scan OpenAPI in the side menu.
- Folder: Click Choose project folder and select the repository root.
- Analyze: Click Analyze API and wait for the result card to appear.
- Result: Review the summary and copy or import the generated
openapi.json. - Upload (optional): Select a workspace and click Upload OpenAPI.
Compatible stacks
The engine automatically recognizes the following ecosystems:
- Java: Spring Boot
- PHP: Laravel
- Node: Express, Fastify, NestJS, Hono
- Python: Django REST, FastAPI, Flask
- Go: Gin, Echo, Chi
- Rust: Axum, Actix
- C#: ASP.NET Core
Advanced options: Infer schemas with AI
| Feature | Structural scan | + Optional AI |
|---|---|---|
| HTTP routes | Yes | Yes |
| DTOs/Models | If in repo | Yes + extra inferred sample |
| Model (~4GB) | Not needed | Required |
| Privacy | Fully local | See privacy |
Best practices
- Point to the API root folder, not the full monorepo.
- Use standard file names (
*Controller.java,routes/*.js, etc.) to facilitate detection. - AI should only be enabled if types are missing and you have no native sources (like SpringDoc).
Cleanup
Clean artifacts lets you delete old analyses (older than 7 days) saved to local disk.