#openapi

Most frontend apps talk to a backend that already has an OpenAPI description. Yet a lot of us still...

I built a diff tool that compares two OpenAPI specs and reports breaking changes — removed endpoints,...

An OpenAPI spec is a JSON or YAML document that describes an HTTP API in a standard,...

Postman is cloud-first and collaborative, Bruno keeps plain-text collections in git, and a local-first OpenAPI studio makes the spec the source of truth. This piece maps where each one wins, where each one silently drifts, and gives a decision checklist based on where your team keeps the contract rather than on UI polish.

A hand-saved API example and a recorded mock drift from the OpenAPI spec after a field rename, a new required field, or an enum change. The mock never enforces the schema, so the old payload stays green locally and fails against the deployed backend. This piece covers why a stale example reads as correct, the signatures of request and mock drift, and the local gate that keeps examples tied to the spec.

I documented a small open-source app, Quiz Tracker, with Thally and published it at...

Most API breakage does not come from a dramatic rewrite. It comes from a small change that looked...

With @panth977/routes, each Node.js endpoint is declared once with zod request and response schemas. That one declaration is the typed handler Express

Why committing generated OpenAPI types makes them a frozen snapshot that typecheck cannot defend against, how a dropped field reaches production under green CI, and the cheap regenerate, replay, and runtime-check habits that catch spec drift before merge.

When an AI agent reads an OpenAPI spec, it picks the first server URL. That is almost always prod. Pinning baseUrl in the gateway per environment beats fighting the agent's prompt.

Why hand-maintaining an MCP tool array next to your OpenAPI spec guarantees drift, and how a gateway that re-derives tools from the spec removes the second artifact you have to keep lying.

Why the upstream credential belongs in the hosted MCP gateway, what leaks when it lives in local config files, and how rotation changes once it does.