Most API workflow pain is not about sending the request.
It is about everything around the request.
The docs live in a README. The real payload shape lives in the backend. The manual test lives in a GUI collection. The CI check lives in a shell script. Then a coding agent enters the project and has to reconstruct the same route, auth rule, and expected response from scattered clues.
That fragmentation makes drift the default.
A useful way to reduce it is the API notebook pattern: keep the explanation, runnable request, expected response, assertions, and workflow notes in small files inside the repository.
