API docs as code: executable contracts in your repo
A practical guide to API docs as code using Markdown contracts that developers can review, coding agents can read, and CI can execute.
CI API testing with Markdown specs
How to run CI API testing with Markdown API specs, stable exit codes, JUnit reports, and secrets passed through RQB_* environment variables.
Read the CI API testing guide →
Writing agent-ready API docs in VS Code
A practical VS Code workflow for authoring Reqbook specs with variable autocomplete, previews, and agent context before coding agents touch the API.
Read the VS Code agent docs guide →
API testing in VS Code with runnable Markdown specs
How the Reqbook VS Code extension lets you preview, validate, run endpoints and flows, and inspect API test results without leaving your editor.
Read the VS Code API testing guide →
API flow testing for onboarding and checkout
How to design multi-step API flow testing for onboarding, checkout, auth, and webhooks using Markdown pipeline specs with captures and injections.
Read the API flow testing guide →
MCP API testing for AI agents
How MCP API testing lets Claude Code and other coding agents search specs, run endpoints, inspect compact results, and avoid copying curl commands.
Read the MCP API testing guide →
API testing for coding agents
A practical workflow for giving Claude Code, Cursor, Copilot, and Codex executable API contracts instead of stale docs and copied curl commands.
Read the API testing for coding agents guide →
Variables and secrets for local API testing
How to handle API testing variables, local secrets, environment files, RQB_* CI variables, and dry runs in a local-first API workspace.
Read the variables and secrets guide →
Markdown API testing that runs
How runnable Markdown API specs turn request examples into executable contracts, local UI screens, CI checks, and coding-agent context.
Read the markdown API testing guide →
A local-first API workspace for agent workflows
Where Reqbook fits when API docs, tests, PR review, CI, and coding-agent context need to stay in sync.
Read the local-first API workspace guide →No posts in this category yet.
Executable API docs belong next to the code.
Markdown specs, CLI runs, local UI, CI, and coding-agent context stay in one repo-native loop.
Install Reqbook →