add-public-endpoint

It scaffolds new public API routes in Next.js applications by generating boilerplate code while enforcing visibility checks and rate limiting for secure unauthenticated access. This creates read-only endpoints suitable for public-facing features.

Exposing unauthenticated endpoints requires visibility checks and rate limiting middleware to secure public access. The scaffolding process integrates user data caching and route matching to ensure only intended data is accessible.

Yes, you can create a read-only public gallery endpoint for unauthenticated users by scaffolding the `/api/public/gallery/:username` route. This automatically includes the necessary security checks and rate limiting for public access.

Yes, scaffolding public API routes includes rate limiting middleware integration to prevent abuse of unauthenticated access. It also enforces visibility checks and user data caching to secure the read-only endpoints.

Use a public endpoint instead of an authenticated API route when exposing read-only data, like a user gallery, to unauthenticated visitors. This approach requires visibility checks and rate limiting to secure the public-facing features.