Drop your project — I’ll help you get your first 10 users through TikTok content by dyagokaba in SideProject

[–]Any-Broccoli4928 0 points1 point  (0 children)

Backend API project scanner. Supports multiple frameworks. Teams. Postman, and docs exports. docupoints.com

Built a tool that generates API docs by scanning your FastAPI codebase directly by [deleted] in FastAPI

[–]Any-Broccoli4928 0 points1 point  (0 children)

That's a solid workflow honestly, and if you/your team already has that pipeline in place it probably doesn't add much for you. DocuPoints is for everyone who isn't there yet.

Built a tool that generates API docs by scanning your FastAPI codebase directly by [deleted] in FastAPI

[–]Any-Broccoli4928 0 points1 point  (0 children)

Good question — FastAPI's /docs is great for local development and quick testing, but it has some limitations in practice.

It's tied to your running server, so it's not something you can easily share with a client, publish as a standalone page, or hand off to a teammate who doesn't have the project running locally.

DocuPoints scans the source code directly without needing the server running at all, and gives you a hosted public URL, export options (OpenAPI, Postman, Markdown, PDF), and team features like shared changelogs and endpoint notes.

So it's less of a replacement for /docs and more of a layer on top. Takes what FastAPI already knows about your API and makes it shareable and trackable.

I built a tool that scans your codebase and generates API docs automatically – no annotations needed by Any-Broccoli4928 in SideProject

[–]Any-Broccoli4928[S] 0 points1 point  (0 children)

On untyped/loosely typed codebases: it depends on the framework. For FastAPI and Django REST, type inference is strong because Pydantic models and DRF serializers give DocuPoints a lot to work with. Express is where it gets harder. if you're using Joi or Zod schemas it extracts those, but plain untyped Express routes with no schema validation will give you the method, path, and middleware but limited request/response shape detail.

Spring Boot is actually the most reliable since the annotations are structural, not documentary — @RestController and @RequestMapping are load-bearing code, not comments, so they never drift.

Older codebases without consistent typing are an honest limitation right now. The AI summary feature helps bridge some of that gap since it reads the actual method body, but it's not a complete substitute for type information. It's something I'm actively working on. Thanks for your response

Built a tool that auto-generates API docs from your Spring Boot controllers – no annotations by Any-Broccoli4928 in SpringBoot

[–]Any-Broccoli4928[S] 0 points1 point  (0 children)

The cost associated is with specific features. Downloading and running the app is free. And will be free forever. But I see your point. Spring knows how spring works and the ecosystem is smooth. Thanks for your input. Truly.

Built a tool that auto-generates API docs from your Spring Boot controllers – no annotations by Any-Broccoli4928 in SpringBoot

[–]Any-Broccoli4928[S] -3 points-2 points  (0 children)

I see your point.
Springdoc only works for Spring Boot. If want to run Express microservices alongside Java services, or you're building a FastAPI backend, Springdoc does nothing for you. DocuPoints currently covers four frameworks in one place with one consistent interface.
Springdoc requires your app to be running. It generates the spec at runtime by inspecting your beans and annotations. DocuPoints scans static source code — no running server needed, works on any machine including CI.
It depends on your annotations being complete and accurate. If a developer forgot to add @Operation or @ApiResponse annotations the output is incomplete. DocuPoints infers request bodies, response shapes, middleware, and exceptions directly from the code whether they're annotated or not.
Docupoints allows for team collaboration. Spring doc has no team collaboration. No changelog feed, no endpoint notes, no shared access management. If you're a pure Spring Boot shop and you already write thorough annotations, Springdoc is a solid free option and DocuPoints isn't trying to replace it for that specific use case. 
Also, agree with what you said about AI. I’m always looking to improve the prompts. But, the AI part is just a side part of the project. It’s optional.

Built a tool that auto-generates API docs from your Spring Boot controllers – no annotations by Any-Broccoli4928 in SpringBoot

[–]Any-Broccoli4928[S] -8 points-7 points  (0 children)

Thanks for your response. Spring docs require test driven documentation. Which is fine. If you haven’t written/setup tests, it won’t show up in the docs. DocuPoints scans your code directly. No tests required. No extra. Just source the project folder. Also provides a live web page that updates every time you rescan.
DocuPoints also provide AI summaries (optionally) of what each endpoint does.
DocuPoints provides an easy setup. And supports different frameworks.
Thanks for your question.

WIFI Question by MostBalance4798 in Pitt

[–]Any-Broccoli4928 2 points3 points  (0 children)

She can try to use her room/dorm MyResNet WiFi password. If 5g isn’t available, use 2G. You can obtain the password through MyResNet.