Most developers I know use at least three tools for a single API.
Postman or Insomnia for sending requests. Notion or a static site for
documentation. And some custom script — or a lot of manual copy-pasting
— for handling auth like HMAC signatures or chained tokens.
None of them stay in sync. The docs go stale. The auth scripts break.
And every new teammate has to figure out the whole setup from scratch.
That's why I built APIKumo.
What it is
APIKumo is an API workspace that covers the full lifecycle in one place:
- Request builder — Monaco-powered editor, collections, environments, multi-tab, 20+ code generation targets
- Pre/Post processors — automate auth before requests fire. HMAC signing, bearer token from env, JSONPath extraction, variable chaining, response assertions. No external scripts.
- Doc publishing — publish to your own subdomain with version selector, changelog, scroll-spy navigation, and a live try-it console
The part I'm most proud of: Docs
API documentation has a reliability problem. You write it once,
it drifts from the actual implementation, and nobody trusts it after a month.
APIKumo generates docs directly from your requests and schemas —
so they stay accurate by default, not by discipline.
Every published collection also gets:
AI chat grounded in your real endpoints
Users can ask questions inside your doc page and get answers based on
your actual API definition. Not hallucinated. Not generic.
Automatic MCP endpoint
Every collection exposes a Model Context Protocol endpoint with zero
configuration. Claude, Cursor, Continue — any MCP-compatible AI agent
can read your API surface and call it natively.
The goal: docs shouldn't be a static page you maintain by hand.
They should be a living surface that works for both humans and AI agents.
Where it stands
APIKumo is free while in preview. I'm actively building and would
genuinely love feedback — especially from developers who've felt this
pain before.
Also launched on Product Hunt today if you want to support or leave feedback there.
What's the biggest pain point you've had with API tooling?
Would love to hear in the comments.
Top comments (0)