72
What if we had a tool that combined the simplicity of curl and the power of Obsidian?
A few months ago, we open-sourced Voiden.
It’s now at ~12k installs, mostly from developers who ran into the same frustration we did: API tooling slowly turning into cloud platforms with accounts, sync, proprietary formats, and static request builders that don’t really reflect how we actually build software.
We tried a different direction.
The key shift is flexibility and composability.
Most API tools lock you into fixed forms and rigid UI flows. Voiden doesn’t.
Instead of a predefined interface, you get a programmable workspace:
slash commands, reusable blocks, and composable primitives that let you shape the tool around your workflow, not the other way around.
You’re not filling out requests in a UI. You’re building your own interface.
Composability over fixed forms
No static request builders like Postman-style UIs
APIs built from reusable blocks (auth, endpoints, params, bodies, scripts)
Everything versioned and composed in Git
The tool adapts to your workflow, not vice versa
Terminal-first execution
A Voiden Runner to execute workflows directly from the terminal
Treat API workflows like scripts, not UI state
Workflow-native by design
Chain requests into flows instead of isolated calls
JS / Python / Shell scripting before and after requests
Single-source workspace
Specs, docs, tests, requests in the same Markdown files
No split between documentation, client, and automation tools
Extensible & programmable
Slash commands + composable primitives
Plugin system built on plain text workflows
SDK for community extensions
Agent-friendly from day one
No proprietary formats
No hidden UI state
Fully readable, generatable, and executable from files
We open-sourced it because we wanted something closer to how developers already work: files, Git, and the terminal — not another siloed platform.
If you’re coming from Postman, Insomnia, or OpenAPI-based setups, you can migrate gradually by importing existing collections/specs into Voiden Markdown and evolving them in-place without breaking your current workflows.
Curious what others think:
What’s still painful in your API workflow today?
What tools are you sticking with, and why?
What would “fully programmable API tooling” need to get right for you?
Happy to hear thoughts.
Built with