I am building Reqbook because API knowledge often gets split across too many places:
- docs explain the endpoint
- Postman or curl sends the request
- CI tests check a small slice
- coding agents get separate prompt context
- PR reviewers see only the code diff
Reqbook tries to make one artifact do more work: runnable Markdown API specs that live in the repo and can be read by humans, run in CI, and used as coding-agent context.
I will mostly write about API docs as code, executable documentation, MCP/CLI tradeoffs, and practical API testing workflows.
Top comments (0)