Git Sync and Version Control: Insomnia vs Plain OpenAPI Files
Quick answer: Version control is where an API workflow either becomes a normal engineering artifact or a siloed, proprietary one. Git sync in a client is useful only when it
Read articleThe Powerduck Blog
API engineering, from the spec out
Product updates, engineering notes, and guides for designing, debugging, testing, mocking, and serving MCP tools from one OpenAPI spec.
Browse the guidesEnvironment Variables and Secrets: Hoppscotch vs a Local Vault
Quick answer: An API client's environment variables are convenient for non-secret values like base URLs, but storing real tokens in a synced collection puts credentials in a place
Read articlePinning an MCP Server Version: Registry Drift vs a Locked Spec
Quick answer: Pointing an agent at a registry entry that always resolves to "latest" means the tools it calls can change underneath you without a commit or review,
Read articleKeeping Cursor's Rules and the OpenAPI Contract in Sync
Quick answer: Cursor rules and an OpenAPI contract are two sources of truth that will drift the moment they are edited separately, and the agent ends up following whichever is
Read articleHTTPie vs curl vs an OpenAPI Client for Quick Requests
Quick answer: curl, HTTPie, and an OpenAPI client are not interchangeable tools at different points of the same workflow. curl is the universal lowest common denominator for one-off and scripted
Read articleDesigning Cursor Pagination: Why Offset Hits a Wall
Quick answer: Offset pagination is simple and correct for static, small result sets, but it breaks down on live data: as rows are inserted or deleted between requests, pages skip
Read articleGenerated Enums Break When the API Adds a New Value
Quick answer: A generated enum is a closed set by default, so the moment the server adds a value the client did not know about, strict generated code can throw,
Read articleVague Tool Descriptions Make the Agent Call the Wrong MCP Tool
Quick answer: An MCP server can expose every operation correctly and still fail in practice, because the model chooses a tool by reading its name and description. When descriptions are
Read articleThe Happy Path Is Fully Tested; the Error Path Is Never Asserted
Quick answer: A suite that covers every successful response but never asserts a failure gives you a false sense of safety: the happy path is the easy part, and the
Read articleMocking Idempotency: Replaying the Same Key Should Return the Same Result
Quick answer: A mock that returns a fresh resource for every request cannot test the one behavior that makes payment and order APIs safe to retry: idempotency. Replaying the same
Read articleDebugging a 401: The Token Was Valid but the Audience Was Wrong
Quick answer: A 401 that arrives with a structurally perfect token almost always means the signature is fine but one of the token's claims does not match what
Read articleThe Agent Reintroduces a Bug You Already Fixed in an Earlier Session
Quick answer: An agent has no memory of a fix it made in a previous session, so nothing structurally stops it from reintroducing the exact bug you already paid to
Read article