Rentgen

Rentgen

API tests before you write tests

8 followers

Visit website
Rentgen finds API bugs when you have no tests yet. We built Rentgen for one reason: to test APIs before you write any tests. Paste one cURL → Rentgen generates 50–200 edge-case checks (boundaries, invalid data, trimming, headers, CORS, enums, latency). No accounts. No cloud. Fully local. Run it before handing the API to QA. Because “the API works” usually means it worked for one happy request.
Rentgen gallery image
Free
Launch tags:API•Developer Tools•Development
Launch Team
Wispr Flow: Dictation That Works Everywhere
Wispr Flow: Dictation That Works Everywhere
Stop typing. Start speaking. 4x faster.
Promoted

What do you think? …

Liudas Jankauskas
Maker
📌
I built this after years of hearing “the API works” — only to discover later that it worked only for one happy request. Most tools help you send requests. Very few help you understand whether your API is actually healthy, predictable, and safe once things go wrong. Rentgen was built to answer uncomfortable questions early: Why does this return 200? Why is this so slow without load? Why does this break with slightly wrong input? Curious to hear how others approach API testing beyond manual requests and scripts.