I stopped hand-writing endpoint docs and just pasted a list instead.

Writing API docs by hand is the task every developer agrees is necessary and nobody wants to do. You ship the endpoint, it works, and then the docs sit stale because documenting it means reconstructing the request shape from memory three days after you wrote it. For internal tools, the cost is a teammate reading your code instead of a reference.

APIDocGen takes the boring part off your plate. You paste a list of endpoints and it produces a Markdown reference with request examples and auth notes. The output covers curl, JavaScript, and Python snippets, so the person consuming your API can copy a call in whatever they are using without translating your mental model into theirs. It is copy-ready — the idea is you paste the result into a repo wiki or a README and ship it, not that you spend an hour reformatting.

For the kind of team shipping internal tools on a deadline, that is the whole value proposition: the docs exist at all, and they exist today, because writing them was a paste instead of a project.

Where AI does belong in this picture

Turning a bare endpoint list into readable prose with examples is the open-ended case where a model helps. There is no single correct wording for "this endpoint returns a paginated list," only a clear one, and generating the three language variants by hand is pure repetition. The structure is yours; the writing labor is not.

What it deliberately does not do

• It documents what you list. It will not discover parameters you left out of your endpoint list, and it will not know about a field your real response returns but you did not mention. The reference is only as complete as the input.
• It does not test the endpoints. The curl, JS, and Python examples are generated from your descriptions, not from a live call. An example that looks right can still fail against the real server — verify before you trust it.
• It is not a hosted API reference platform. Markdown in a repo is the format. If you need interactive docs, versioned portals, or auto-sync from a spec, that is a different (heavier) tool.
• Auth notes are reminders, not a security review. It will note that an endpoint needs a token; it will not tell you whether your auth scheme is correct.

If your internal endpoints are undocumented because writing docs is a chore, APIDocGen is $19/mo and turns a list into a Markdown reference you can actually ship.