Cursor workflow

API testing for Cursor

Use runnable markdown API specs in Cursor so endpoint changes, request examples, and CI validation stay in the same repo workflow.

Install Reqbook Read the markdown API testing guide

Make API specs visible to Cursor

Cursor works best when the important context is already in the repository. Reqbook stores API testing specs as markdown files so Cursor can inspect request payloads, expected responses, variables, and notes without relying on a hosted collection.

Repo-native

Endpoint contracts live in Git beside handlers, DTOs, routes, and integration tests.

Executable

Cursor can use rqb exec to run a spec instead of rebuilding curl commands from scratch.

Reviewable

Markdown API specs are easy to diff and review in pull requests when Cursor changes an endpoint.

Cursor API testing workflow

After installing Reqbook skills, keep the API loop inside files and commands Cursor can reason about.

$ rqb skills install --agent=cursor
$ rqb exec api-docs/users.md
$ rqb validate api-docs/
  • Ask Cursor to check the endpoint spec before changing route behavior.
  • Update the markdown request and expected response when payloads change.
  • Run validation before the pull request so examples do not drift from implementation.

Why markdown API testing fits Cursor

Cursor can read files better than it can operate hidden app state. A local-first markdown API client gives Cursor a durable contract that survives each session, works offline, and can be validated in CI.

Learn the broader pattern in API testing for coding agents, or see how Reqbook fits an agent-native API workspace.