Topic
A real integration walkthrough: import the vendor OpenAPI file once, let the assistant and your coding agent read the exact contract, and send real requests locally, with no more curl archaeology in chat windows.
Read articleThree ways to recover a spec from a running codebase: annotations, traffic recording, and AST scanning. We compare what each extracts across eight languages and 28 frameworks, and why honest gaps beat confident guesses on request bodies.
Read articleThe create call returned 200, the detail view 404s, and cancel accepts an illegal state. Scenario tests chain real calls, pass data between steps, and hand the agent evidence to fix with.
Read articleA folder of requests that each return 200 is not a test suite. A scenario chains requests the way a user walks the product: create, capture, poll, act, assert. Here is how to derive scenarios from an OpenAPI spec and run them against mock then staging.
Read articleA concrete sprint diary: one OpenAPI file drove a local mock with latency and error overrides, a four-step checkout scenario with an HTML report, live docs, derived database tables and a hosted MCP endpoint while the real API did not exist yet.
Read articleFake objects in components demo well and integrate badly. Agree on the coupon validation contract first, then let a spec-driven mock answer real HTTP while the service is still being built.
Read articleGenerated screens fail on limit versus pageSize, data.records versus data.items, cents versus dollars. The fix is not a better prompt; it is letting the agent query the real contract and verify against real responses.
Read articleA request that runs is the start of a handoff, not the end of one. Import the curl, capture the missing context, and promote what you learned back into the specification.
Read articleReal systems are multi-protocol: REST at the edge, WebSockets for events, gRPC between services, GraphQL at the gateway. Powerduck debugs all of them from the same workspace and the same spec.
Read articleThe field changed in code, in chat, and in the HTTP client while the docs waited for someone to care. A local OpenAPI file in version control gives the whole team one contract to diff, review, and trust.
Read articlePostman collections, mock servers, docs generators and MCP glue all drift the moment the spec stops being the source of truth. Powerduck keeps one local OpenAPI file at the center.
Read articleA 4,000-line YAML file is unmaintainable, but splitting a spec wrong creates a web of relative refs that no editor or bundler can resolve. Here is a folder layout that scales past 200 operations, the $ref conventions that keep it sane, and the CI checks that keep it honest.
Read article