Install
API Design & Governance
Naming, pagination, filtering, errors, versioning, and style guides at scale.
- 3 Tracked terms
- Last 30 days Feed window
What this topic collects on
An article joins this feed when it matches these terms. Each one is also a search of its own.
Related topics
Latest in API Design & Governance
I got tired of OpenAPI generators breaking my clients, so I built steadysdk
1+ day, 11+ hour ago (106+ words) Most OpenAPI generators are "generate once and forget." You run them the first time and everything looks great. Then the backend changes an operationId, adds an endpoint, or renames a field… and suddenly: I got tired of this cycle, so…...
oRPC Releases Version 1.0 with OpenAPI Support and End-to-End Type Safety
3+ day, 21+ hour ago (424+ words) QCon AI Boston (July 8-9, 2027): Agents. Context. Evals. Security. See how other teams make decisions. Register Now Susan Chang explains how Elastic transitioned from siloed, ad-hoc AI agent evaluations to a unified, production-grade framework. She discusses balancing LLM-as-a-judge with deterministic rules,…...
My OpenAPI changelog generator found 1,900 breaking changes — a formatter had just reordered every key
1+ week, 2+ day ago (206+ words) I built an OpenAPI changelog generator because API release notes are miserable to write by hand: diff two specs, get a structured list of breaking changes — removed paths, changed types, new required fields. The first real run humbled me. I…...
OpenAPI agent-ready docs ZIP in one click (llms.txt, MCP stubs, Postman)
2+ week, 6+ hour ago (136+ words) Agents don't browse Swagger UI the way humans do. They need structured maps, tool stubs, and copy-pasteable examples — not a wall of endpoints meant for clicking. SpecPack (openapi-agentpack) takes an OpenAPI 3.x spec (drop a file or paste JSON/YAML)…...
OpenAPI Specification | Sapling.ai Developer Documentation
2+ week, 1+ day ago (218+ words) Sapling publishes a machine-readable OpenAPI 3.1 description of its REST API: The spec describes the public endpoints you can call with an API key: Operations are grouped by tag (proofreading, generation, detection, analysis, files, account, service), so generated clients get one…...
I diffed GitHub's, Stripe's and OpenAI's OpenAPI specs. Three vendors, three totally different change regimes.
2+ week, 4+ day ago (384+ words) Method: for each vendor, two commits of their spec repository — a baseline and a current one — counted operations, and looked at what was removed or newly marked deprecated between them. The commit shas are below so you can reproduce this…...
I turned a real OpenAPI into an MCP server in 5 min (without losing custom code on regen)
3+ week, 1+ hour ago (145+ words) I built an OpenAPI to MCP server generator for TypeScript, Python and Go. The v1 mistake: 1 endpoint = 1 tool. On a real API with 200 operations, you get a 200-tool server. Nobody can use that. That was the exact feedback I got on…...
We scanned 1,939 repositories. 95% of projects publishing an OpenAPI spec have no compatibility gate.
3+ week, 1+ day ago (1184+ words) We went looking for projects that publish an OpenAPI specification and then let anything through CI unchecked. We expected a niche. We found the default. Of 85 repositories with a genuine first-party OpenAPI spec, exactly four run any breaking-change detection at…...
Your OpenAPI spec is a contract. Nobody is checking it. I built a CLI that detects spec↔code drift with zero dependencies.
3+ week, 1+ day ago (358+ words) An OpenAPI spec is not just documentation. SDKs, frontend types, API docs, mock servers — everything is generated from the spec. When the implementation drifts from it, everything generated starts lying quietly. This is about oas-drift, a CLI I built that…...
Virtual sandbox from Swagger spec: build a working OpenAPI mock
3+ week, 2+ day ago (178+ words) You have an OpenAPI file. The frontend needs an API URL today. The backend is still being built. For this walkthrough, I uploaded a small product catalog spec to Beeceptor and called the generated routes. GET /products returned HTTP 200 with…...