Design your API once. Let Claude, Cursor,
and your team call it instantly.
APIKumo gives you a Postman-style workspace, auto-generated docs, and a live MCP endpoint — without juggling Postman, Mintlify, and a hand-coded MCP server.
Why developers switch to APIKumo
You build APIs — AI agents need to call them
- Every published collection becomes a live MCP endpoint, zero config
- Claude, Cursor, and Continue discover your API surface automatically
- llms.txt + Markdown export in one click
Switching from Postman? You'll be set up in minutes.
- Import Postman v2.1 — schemas, environments, and auth all carry over
- Pre/post processors match what you already know (HMAC, JSONPath, custom JS)
- Fraction of the price of Postman Team
Ship docs your users actually want to use
- Custom subdomain + theme + AI chat — no Mintlify subscription needed
- Versions + changelog built in
- Try-it panel works with real auth, environment-aware variables
A keyboard-first editor built for your workflow
- Cmd+K palette, multi-tab, Monaco body editor with format-on-paste
- CORS-free proxy, per-workspace environments that never leak secrets
- Code samples in 27 languages, one click to copy
Three panes. No clutter.
Sidebar for collections, editor for the active request, response below. Calm typography, generous spacing, one accent color.
- 16px monospace URL bar with inline {{variable}} chips
- HTTP methods color-coded the same way in sidebar, editor, and docs
- Resizable sidebar and split, restored across reloads via local settings
- WCAG-AA contrast on the dark theme — your eyes get a break
{
"id": "usr_8f2a",
"name": "Ada Lovelace",
"role": "admin",
"createdAt": "2026-04-29T09:12:00Z"
}Create a user
Creates a user record in the active tenant. The caller must have the users:write scope.
fetch("/v1/users", {
method: "POST",
headers: {
"Authorization":
"Bearer " + token,
"Content-Type":
"application/json"
},
body: JSON.stringify({
name: "Ada",
role: "admin"
})
})Authorization header. See POST /v1/users for an exampleShip docs that look like a product.
Every collection can become a public docs site on its own subdomain — with a theme, search, scroll-spy navigation, and live try-it. No static-site generator, no markdown rewriting.
- Custom subdomain — publish to
your-api.apikumo.comand share a single link. - Versions & changelog — snapshot v1.0, keep editing v1.1, and show readers what changed.
- Permalinks everywhere — /endpoints/users-create, plus llms.txt, OpenAPI, and Markdown exports.
- Try-it panel — readers can call your API from the docs page, with env-aware variables and auth.
- Reader sign-in — visitors can sign in with Google, GitHub, or Discord directly on your docs site.
The details, without the scroll.
Code samples, import/export formats, and keyboard shortcuts — one panel, switch to what you need.
How APIKumo stacks up
One tool for testing, docs, and MCP — see how that compares to the tools you might be using today.
Docs and a read-only MCP endpoint in one workspace — free while in preview, no per-seat bill.
Keep a fast API client, and add cloud sync, hosted docs, and an automatic MCP endpoint.
A real API client and a docs platform in one — not just documentation.
One workspace for the entire request lifecycle.
Sign in with a single click and your collections, environments, and settings sync to every device you use.
No card required · Sign in with Google, GitHub, or Discord
What the team is building
How to secure API secrets in APIKumo: Bearer, Basic, and API-key auth without ever hardcoding a value
Onboarding a new developer to your API in under ten minutes using APIKumo's Try-it panel and MCP endpoint
