CChosen Vincent2d ago · 20 min readHow to build API documentation with Thally: from setup to a live siteEvery API needs docs, and many teams want to manage them the same way they manage code: in a GitHub repo, reviewed in pull requests, and published automatically. Thally is a docs platform built aroundchosenvincent.hashnode.dev
PPowerduck3d ago · 4 min readPostman vs Bruno vs a local-first OpenAPI studio: choose by where the spec livesTeams pick an API client out of habit and then spend months paying for a model that never matched how they actually work. The split between the common choices is not the pretty UI. It is where the conblogs.powerduck.com
PPowerduck3d ago · 5 min readYour saved API example keeps passing against the mock and fails against the live backendYou keep one saved request in your API client for the create-order flow. You open it, hit send against the local mock, see a 200, and move on. A week later that same request against staging comes backblogs.powerduck.com
AAbhinav Sharma5d ago · 4 min readThe API change that looked harmless in reviewNobody on the team thought the change was risky. One field removed from a response. One header now required. The diff was four lines, the tests passed, two people approved it. What nobody could see inimpactgate.hashnode.dev
PPowerduck5d ago · 4 min readThe Agent Bumped a Major Version and CI Stayed GreenThe PR looked like housekeeping. The agent bumped one dependency across a major version, updated the lockfile, described it as "chore: upgrade queue-client to v4," ran the suite, and merged. CI was gr1Ablogs.powerduck.com
PPowerduck5d ago · 4 min readWe Committed the Generated Types to the Repo; CI Stayed Green While the Server Dropped the FieldA customer reported that a profile screen showed a blank subscription tier. The SDK compiled, unit tests passed, CI was green on the branch that shipped. At runtime the code read profile.plan and got blogs.powerduck.com
PPowerduckOct 18 · 4 min readWhen the Spec Changes, the MCP Tool List Should Change With ItThe first MCP server we stood up, someone on the team wrote out the tool list by hand. A JSON file with 22 entries, each describing one endpoint we wanted the agent to reach. Names, descriptions, inpublogs.powerduck.com
PPowerduckOct 18 · 4 min readPin baseUrl in the Gateway, Not in the Agent's PromptThe other day an agent I was testing kept hitting production. Not on purpose, not because it was being clever. It was reading the OpenAPI spec we handed it, picking the first entry in the servers arrablogs.powerduck.com
PPowerduckOct 18 · 4 min readStore the Upstream Token in the Gateway, Not in Your MCP ConfigWhen we first wired billing into the agent, the config looked like this: { "mcpServers": { "billing": { "command": "npx", "args": ["-y", "@powerduck/openapi-mcp-server", "serve", "--blogs.powerduck.com
PPowerduckOct 18 · 4 min readExpose Three Operations, Not the Whole OpenAPI SpecThe first time we wired billing to an agent, we converted the whole OpenAPI document. Every path, every method, every tag. 87 tools showed up in the client. It felt generous — look at all the things tblogs.powerduck.com
