Odd Bits / Builder kits
CLI Maker
Drop in the OpenAPI (or Swagger) spec of an API and get a command-line tool for it: one command per operation, flags for the parameters, help text, and a welcome screen you design. It is a working starting point you can read and edit, not a finished product.


- What you get
- A command tree and generated code for your API
- A welcome screen you design
- The full project as a zip with README and tests
- Works with
- OpenAPI 3.xSwagger 2.0JSON or YAML
- Version
- v1.0, updated 2026-10-19
1. Your API spec
OpenAPI 3.x or Swagger 2.0, JSON or YAML, up to 10 MB. Or paste it below.
2. Welcome screen (free to copy, no spec needed)
What your CLI prints when someone runs it with no arguments in a terminal.
█ █ █ █ ████ █ █████
██ ██ █ █ █ █ █
█ █ █ █ █████ █ █ █
█ █ █ █ █ █
█ █ █ ████ █████ █████
A small CLI for a big API.What it never does
- Upload your spec or send any part of it to a server
- Fetch a spec from a web address (paste it or choose the file)
- Put telemetry or any call home in the generated CLI
- Promise the generated CLI is finished or production-ready: read it and test it before you ship it
Questions
What do I get?
A TypeScript project for Node: a package.json with a bin entry, a command per operation grouped by tag, flags for path, query and body parameters, --help everywhere, a --json option, config for the API key or token, a README and a couple of tests.
What does the free preview show?
The command list for the whole API, the generated code for the first three commands, and the welcome-screen designer. The designer is always free: copy the banner or the print snippet into any CLI.
Which specs work?
OpenAPI 3.x and Swagger 2.0, as JSON or YAML, up to 10 MB. Very large APIs work best if you trim the spec to the paths you need.
Can the generated CLI do everything my API does?
No. It covers the operations and parameters it can read from the spec, and warns about the ones it cannot. Odd cases (unusual auth, file uploads, streaming) may need hand edits.
OpenAPI and Swagger are named only to say which spec formats this reads. Not affiliated with or endorsed by the OpenAPI Initiative or SmartBear.