voiden
Reduces friction in API documentation and testing workflows by treating API specs as versionable code artifacts, eliminating proprietary tool lock-in and ena…
Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.
- Design REST API endpoints using Markdown syntax without switching tools.
- Test API requests directly in documentation and track changes in Git.
- Document multiple API versions side-by-side and reuse common request blocks.
Reduces friction in API documentation and testing workflows by treating API specs as versionable code artifacts, eliminating proprietary tool lock-in and enabling offline-first collaboration across distributed teams.
Engineering teams managing multiple APIs who need version control, collaborative documentation, and testing without external platform dependencies.
https://github.com/VoidenHQ/voiden
By VoidenHQ
How to Get It
claude plugins install VoidenHQ/voiden
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me design REST API endpoints using Markdown syntax without switching tools
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Hacker News
- Show HN: Voiden – a free, offline, Git-native API Client — Hacker News · 79 pts
- Show HN: Voiden – an offline, Git-native API tool built around Markdown — Hacker News · 48 pts
- Show HN: Voiden – API Workflows as Markdown Files (Obsidian × Curl) — Hacker News · 9 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 1,770 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 1,770 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.