A Free API Documentation Tool, No Catches

“Free” in this category usually means free to start. The viewer itself costs nothing, but the feature you actually want — an interactive request console, a custom domain, a theme that isn’t the default — turns out to live behind an account, a workspace, or a paid tier once you go looking for it.

What “free” usually means elsewhere

A few examples, because the pattern is consistent: ReDoc’s open-source edition renders documentation but gates its interactive Try It Out console behind ReDoc+, Redocly’s paid product. Scalar’s core API Reference viewer is open source, but newer functionality increasingly lives behind Scalar Cloud, its hosted tier. Postman’s docs feature is free to start, but publishing requires a Postman account and workspace, and a custom domain for the published page is a paid-plan feature. None of this is false advertising — the free tier is real — but “free” and “everything” aren’t the same word in any of these tools.

What free means with GetMan

GetMan is MIT-licensed, full stop. Try It Out, dark mode, the ⌘K command palette, deep links to individual endpoints and schemas — none of it is split into a “core” version and a paid add-on, because there isn’t a paid version to compare it to. There’s no account to create, no workspace to join, and no usage limit that kicks in once you’re past a trial period. You add a script tag, point it at a spec URL, and everything the project ships is already there.

When a paid tool still makes sense

If what you actually need is a platform — hosted mock servers, team-based workspace permissions, API design collaboration — that’s a different product category, and a paid tool built for that job is a reasonable trade for the convenience. But if the requirement is narrower — render a spec, let people try requests against it, on a page you already own — paying for that specifically usually means paying to unlock a feature a free, self-hosted viewer already includes.