01
Write
Keep context and HTTP intent in one Markdown document. Your API notes stop being a separate artefact.
GIT-NATIVE API WORKSPACE
Markdown becomes
executable API docs.
Write the explanation. Write the request. Run it in place. Keep everything versioned as code.
Local-first desktop app · Markdown-first · Git-native
# Users API
Describe the endpoint right where you use it.
<!-- rqm:block id="get-user" name="Get User" -->
```reqmark
GET https://api.example.com/users/123
Authorization: Bearer {{token}}
Accept: application/json
```GET /users/123
02
Execute
Run a request beside its documentation and see the result without leaving the workspace.
03
Inspect
Review status, headers, response bodies, duration, size, and errors in one focused panel.
04
Version
Commit the requests and the documentation together. Your API workspace becomes part of the codebase.
THE .RQM FORMAT
Human-readable first.
Executable when you need it.
DocsMarkdown
RequestsGET · POST · PUT · PATCH · DELETE
VersioningGit
RuntimeDesktop · Local-first
READY WHEN YOU ARE
Stop describing API requests from a distance.
Put the documentation and the request in the same room.
Get Reqmark