SDKCraft turns your OpenAPI spec into a production-ready SDK in seconds. ✅ TypeScript, Python, Go, Dart & Java ✅ Code preview before downloading ✅ Download as ZIP ✅ CLI: npx sdkcraft --input api.yaml --lang typescript ✅ API Change Detection ✅ AI Documentation Generator Free & open source. No signup required.
No reviews yetBe the first to leave a review for SDKCraft
Maker
📌
Hey Product Hunt!
I built SDKCraft because I was tired of writing the same boilerplate API clients over and over again.
Upload your OpenAPI spec → pick your language → get production-ready SDK code in seconds.
Supports TypeScript, Python, Go, Dart & Java. Free & open source!
Would love your feedback — what languages or features should I add next?
Report
😹 LOL
Honestly pretty cool, threw my OpenAPI yaml at it and got a usable typescript SDK in like a minute. The CLI one-liner is really convenient, no signup stuff is a nice touch too.
Report
Maker
@araczeliha97691 Appreciate this — a minute from yaml to usable SDK is exactly the experience we're going for. And yeah, the no-signup CLI flow was a deliberate choice; didn't want friction getting in the way of just trying it out. Glad it landed well for you!
Report
💎 Pixel perfection
Finally tried this on a messy OpenAPI spec I'd been avoiding and the TypeScript output was actually clean and usable right away, no cleanup needed.
Report
Maker
@abantalasvqx0 This is great to hear — messy specs are exactly the stress test we care about most, since real-world APIs are rarely clean. Glad it handled yours without needing manual cleanup. Curious what made that particular spec messy (weird nesting, inconsistent naming, missing types)? That kind of feedback helps us keep hardening the generator.
Honestly pretty cool, threw my OpenAPI yaml at it and got a usable typescript SDK in like a minute. The CLI one-liner is really convenient, no signup stuff is a nice touch too.
@araczeliha97691 Appreciate this — a minute from yaml to usable SDK is exactly the experience we're going for. And yeah, the no-signup CLI flow was a deliberate choice; didn't want friction getting in the way of just trying it out. Glad it landed well for you!
Finally tried this on a messy OpenAPI spec I'd been avoiding and the TypeScript output was actually clean and usable right away, no cleanup needed.
@abantalasvqx0 This is great to hear — messy specs are exactly the stress test we care about most, since real-world APIs are rarely clean. Glad it handled yours without needing manual cleanup. Curious what made that particular spec messy (weird nesting, inconsistent naming, missing types)? That kind of feedback helps us keep hardening the generator.