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.

What if curl and Obsidian had an API baby?

That’s Voiden.

An offline-first, git-native API workspace where everything is plain executable Markdown.

The core idea is composability, not forms.

Instead of fixed request builders, you compose APIs from reusable blocks: auth, endpoints, params, bodies, scripts, flows. Define once, reuse everywhere, and evolve it like code in Git.

From that, a few things naturally follow:

• A Voiden Runner that executes workflows directly from the terminal

• Chaining requests into flows instead of isolated calls

• JS / Python / Shell scripting before and after requests

• Specs, docs, tests, and requests living together in one place

• Plugins built on top of plain text

• An agent-friendly format from day one — nothing hidden, nothing to reverse-engineer

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 “curl + composable editor” need to get right for you?

Happy to hear thoughts.