Okibi builds a CLI from your API's OpenAPI spec, checks it, and publishes it. Agents then suggest improvements you accept or reject. You can drive every step from the web app, from the okibi CLI, or from a coding agent.
Pick your path
Use the web appPaste an OpenAPI link or file, docs, or a public repo, and get a working CLI.Use the okibi CLIInstall okibi, log in, and run
okibi generate from any directory.Let your agent do itPaste one prompt into Claude Code or Codex. The agent installs okibi and runs the generation for you.What every generated CLI includes
- Typed commands for your API, grouped by resource.
- Human output by default, JSON on request, with meaningful exit codes so scripts and agents can rely on it.
- Generated command docs and a SKILL.md that teaches agents how to use it.
- A hosted MCP server, so agent clients can call the CLI without installing it.
- Installable releases behind a one-line installer.
Each release passes automated build, vet, shipcheck, and live dogfood checks before it ships.
How these docs are organized
| Section | Read it when you want to |
|---|---|
| Get started | Build your first CLI and learn the moving parts |
| Guides | Create, review, release, and share a CLI, in the app or the terminal |
| The okibi CLI | Install, log in, and script the okibi client |
| Command reference | Look up any okibi command and its flags |
| For agents | Hand Okibi to a coding agent |
| Help | Fix a problem, read the FAQ, or see what changed |