The latest articles on DEV Community by eknut w. (@eknut_w_22173d7fbba4f987). https://dev.to/eknut_w_22173d7fbba4f987 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3922774%2F96aca30e-a080-4086-a9a2-186e1c0617e0.jpg https://dev.to/eknut_w_22173d7fbba4f987 en eknut w. Sun, 10 May 2026 04:09:40 +0000 https://dev.to/apikumo/i-built-an-api-workspace-where-docs-write-themselves-with-ai-chat-and-mcp-built-in-269o https://dev.to/apikumo/i-built-an-api-workspace-where-docs-write-themselves-with-ai-chat-and-mcp-built-in-269o <p>Most developers I know use at least three tools for a single API.</p> <p>Postman or Insomnia for sending requests. Notion or a static site for <br> documentation. And some custom script — or a lot of manual copy-pasting <br> — for handling auth like HMAC signatures or chained tokens.</p> <p>None of them stay in sync. The docs go stale. The auth scripts break. <br> And every new teammate has to figure out the whole setup from scratch.</p> <p>That's why I built <strong>APIKumo</strong>.</p> <h2> What it is </h2> <p>APIKumo is an API workspace that covers the full lifecycle in one place:</p> <ul> <li> <strong>Request builder</strong> — Monaco-powered editor, collections, environments, multi-tab, 20+ code generation targets</li> <li> <strong>Pre/Post processors</strong> — automate auth before requests fire. HMAC signing, bearer token from env, JSONPath extraction, variable chaining, response assertions. No external scripts.</li> <li> <strong>Doc publishing</strong> — publish to your own subdomain with version selector, changelog, scroll-spy navigation, and a live try-it console</li> </ul> <h2> The part I'm most proud of: Docs </h2> <p>API documentation has a reliability problem. You write it once, <br> it drifts from the actual implementation, and nobody trusts it after a month.</p> <p>APIKumo generates docs directly from your requests and schemas — <br> so they stay accurate by default, not by discipline.</p> <p>Every published collection also gets:</p> <p><strong>AI chat grounded in your real endpoints</strong><br> Users can ask questions inside your doc page and get answers based on <br> your actual API definition. Not hallucinated. Not generic.</p> <p><strong>Automatic MCP endpoint</strong><br> Every collection exposes a Model Context Protocol endpoint with zero <br> configuration. Claude, Cursor, Continue — any MCP-compatible AI agent <br> can read your API surface and call it natively.</p> <p>The goal: docs shouldn't be a static page you maintain by hand. <br> They should be a living surface that works for both humans and AI agents.</p> <h2> Where it stands </h2> <p>APIKumo is free while in preview. I'm actively building and would <br> genuinely love feedback — especially from developers who've felt this <br> pain before.</p> <p>👉 <a href="https://apikumo.com" rel="noopener noreferrer">apikumo.com</a></p> <p>Also launched on Product Hunt today if you want to support or leave feedback there.</p> <p>What's the biggest pain point you've had with API tooling? <br> Would love to hear in the comments.</p> api webdev productivity ai