Your API Bug Report Is Missing the Caller
A failing request needs its environment, caller, and starting state. Preserve those conditions when handing an API investigation to AI.
Read articleTopic
debugging
Your JSON Is Valid. Your Content-Type Might Not Be.
A practical way to separate request format errors from response negotiation problems, with cURL examples and a four-case regression checklist.
Read articleYour API Works in cURL. Why Does the Browser Reject It?
A practical way to compare a working cURL request with a failing browser request, inspect preflight headers, and verify both success and error responses.
Read articleHow to Test and Debug an MCP Server: From the Inspector to Automated Tool Tests
An MCP server is just JSON-RPC over a transport, which means it is fully testable without an AI in the loop. Here is a practical ladder: Inspector for discovery, curl for the protocol, and deterministic automated tests for schemas, errors, and side effects in CI.
Read articleA curl command is not an API handoff
A 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 articleDebugging HTTP, WebSocket, gRPC and GraphQL without switching apps
Real 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 article