Tootfinder

Documentation continues. Done with the `queue` and `worker` endpoints, probably about 50% of the way done with this. I still need a good way to package all of this up with the binary which means putting the `openapi.yaml` file somewhere on the net so it can be pulled if need be. I'll deal with that later...lol
#openapi

Why using a MCP when you have a clean OpenAPI with consistent results?
#ai #openapi #mcp

📖 Automatic API documentation:
PostgREST generates #OpenAPI specs automatically from your schema. Hook up Swagger-UI − interactive, always up-to-date docs for your API. No more manual doc maintenance.
🏗️ Versioning through DB schemas:
Instead of managing API versions in code, PostgREST uses #PostgreSQL

Now the pain in the ass part: documenting all of the routes. I think I'm gonna use Scalar because it's easy and I'm pretty lazy. Carved off the `/doc` directory to host the `openapi.yaml` and `index.html` files. So far, got one single endpoint documented...lol
#openapi #sisyphus

🔁 RESTful path params like /products/{id}, reverse proxy endpoints (passthrough or transform), HTTP custom types letting #PostgreSQL functions call external APIs directly
🛡️ Enterprise-ready out of the box: authentication, authorization, rate limiting, caching, SSE streaming & full #OpenAPI

🛠️ Code generation with diff preview, cURL builder from captured requests, one-click request replay, VS Code-style command palette (Ctrl K), built-in Swagger UI & dark/light theme with PWA offline support
🌐 Language-agnostic API (#OpenAPI 3.1) - send debug data from #Python,