What is Reqbook?
Reqbook is the notebook for API workflows. It stores API docs, requests, tests, flows, and coding-agent context as runnable Markdown files in your repository.
Answers about Reqbook, the notebook for API workflows: Markdown API specs, local-first installs, CI, agents, imports, secrets, and comparisons.
Reqbook is the notebook for API workflows. It stores API docs, requests, tests, flows, and coding-agent context as runnable Markdown files in your repository.
Because each Markdown spec can explain the endpoint, define the request, show the expected response, capture variables, run assertions, and give agents compact executable context.
Those tools are strongest as API clients and collection workspaces. Reqbook is strongest when the API source of truth should live in Git, run in CI, and stay readable to coding agents.
No. Reqbook runs locally as a Rust binary. There is no hosted workspace or login. Optional anonymous active-usage reporting is off by default.
Use the shell installer, npm package, crates.io package, VS Code extension, Homebrew tap, Windows installer, Docker image, or a source checkout.
Yes. Reqbook ships agent skills and MCP tools so Claude Code, Cursor, Copilot, Codex, Antigravity, Windsurf, and OpenCode can read, run, validate, and update API specs.
Yes. Use rqb validate for spec checks, rqb exec for endpoint execution, and rqb flow for multi-step API workflows.
Yes. Reqbook can import from OpenAPI, cURL, Postman, Insomnia, local client collections, .http files, or scan a project for missing specs.
Keep secrets out of committed Markdown. Use local env files, CI secrets, or RQB_* environment variables while committing templates and non-secret variable names.
Start with the Reqbook install guide and open the browser workspace with rqb serve.
Read Reqbook vs Postman if you are moving from a hosted collection workflow.
Use Claude Code or Cursor guides when agents need API context.