<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenAPI on Restish</title><link>https://rest.sh/categories/openapi/</link><description>Recent content in OpenAPI on Restish</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 07 Jun 2026 20:33:40 -0700</lastBuildDate><atom:link href="https://rest.sh/categories/openapi/index.xml" rel="self" type="application/rss+xml"/><item><title>Turn an OpenAPI Spec Into a CLI Without Generating Code</title><link>https://rest.sh/blog/turn-an-openapi-spec-into-a-cli-without-generating-code/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><guid>https://rest.sh/blog/turn-an-openapi-spec-into-a-cli-without-generating-code/</guid><description>&lt;p&gt;OpenAPI is usually treated as an input to something else. Generate an SDK. Render
Swagger UI. Publish reference docs. Feed a contract test. All of those are good
jobs for a spec.&lt;/p&gt;
&lt;p&gt;But there is another useful job hiding in the same document: teach the terminal
how to work with the API.&lt;/p&gt;
&lt;p&gt;That does not have to mean generating a new repository, choosing a language
runtime, publishing a package, and keeping a client binary in sync with every
operation change. A CLI can load an OpenAPI description at runtime, cache what it
needs, and turn repeated API work into commands without making users rebuild a
client.&lt;/p&gt;</description></item></channel></rss>