Swagger

Swagger is the toolset and, originally, the specification that taught the industry to describe REST APIs in a machine-readable way. The specification itself was donated in 2015 and renamed the OpenAPI Specification, while the Swagger name lives on as the open-source and commercial tooling — Swagger UI, Swagger Editor, and Swagger Codegen — that most developers first encounter. For a lot of teams, “Swagger” is still shorthand for “the interactive docs generated from our API definition,” even though the format underneath is now OpenAPI.

• Swagger UI - Renders an OpenAPI definition into interactive, try-it-out documentation that developers can call directly from the browser.
• Swagger Editor - A design-time editor for authoring and validating API definitions as you write them.
• Swagger Codegen - Generates client SDKs and server stubs from a definition, turning the contract into working code.
• The spec-to-tooling bridge - Swagger’s real legacy is proving that a single source-of-truth contract could drive docs, code, and tests at once.

In practice, Swagger tooling is how a machine-readable contract becomes something people actually use — docs a partner can explore, an SDK a developer can install, a stub a team can build against. Its lasting lesson, which I have written about for years, is that the value was never the brand but the shared definition: once OpenAPI standardized that format, the same contract could feed governance, mocking, testing, and now agent tooling. Swagger UI’s success is why “generate the docs from the spec” is table stakes today rather than a novelty.