I'll be straight: DevBook was built by AI. I know, I know — stay with me.
Because the punchline is that I've spent the last week using it to hammer the OpenAI API, and there's something deeply satisfying about using an AI-built tool to run your own AI experiments faster than you ever could in Postman.
You're not trusting AI. You're making it work for you. Different thing.
It's a browser-based API workbench. No download. No Electron bloat. No $14/seat/month Postman invoice landing in your inbox. Just open devpad-ves9.polsia.app and start firing requests.
Here's what it actually does — no fluff:
API Key Vault
Drop your keys in once — {{openai_key}}, {{stripe_key}}, {{twilio_key}} — and they auto-fill across every template. Zero re-entering. Zero copy-paste accidents.
Template Builder with {{placeholders}}
Write your request once. Mark dynamic parts with {{placeholders}}. DevBook turns them into a real fillable form automatically. Testing gpt-4o vs gpt-4o-mini? Just swap the {{model}} field. No JSON editing. No fat-fingering brackets at 1am.
Split-Screen Response Viewer
Request on top. Response on the bottom. Syntax-highlighted, status color-coded (200 green, 4xx orange, 5xx red), with response time in ms. That's it. That's the feature.
Searchable Request Index
Every template you save is instantly searchable. No folder trees. No collections. No "where did I put that webhook test" moment.
Why this beats the status quo:
Postman made sense when it was free and simple. Now it's a $14/seat/month platform trying to be everything. A team of 5 pays $70/month for what is fundamentally a request-sending utility. That's wild.
On the "AI-built" thing:
Most AI-built tools get bloated fast — throw every feature at the wall, ship it, move on. DevBook went the other way. No environments, no workspaces, no nested collections. It made deliberate choices about what to leave out, and that's honestly harder to get right than adding features.
The result is a tool that does exactly what you actually reach for — and nothing you have to learn around.
Three steps and you're done:
- Add your API keys to the vault
Build a template with {{placeholders}}
Fill, send, reuse. Build your library.
Top comments (0)