Short answer: The inso CLI runs the client's collections and assertions in CI; an OpenAPI CLI works from the contract and can validate, generate, and verify. The first executes the authored set; the second treats the spec as the source and derives the checks.
What a collection CLI is built for
Running the saved requests and their assertions in a pipeline. It is a reliable runner for a fixed set and is only as current as the collection.
What a spec CLI is built for
| Task | Collection CLI | OpenAPI CLI |
|---|---|---|
| Run authored requests | Yes | Generated |
| Validate the contract | Not its job | Yes |
| Generate surfaces | No | Docs, mocks, tools |
| Verify conformance | Assertions | Schema check |
Why the source matters
A spec CLI starts from the artifact that changes with the API, so the checks cannot run against a stale collection. A collection CLI is a runner for a snapshot.
How they fit
Keep the collection CLI for fixed behavioral calls and use the spec CLI for validation and generation. The runner and the source are different concerns.
This is part of the Powerduck vs Insomnia comparison. Finish with collections vs generated.
Top comments (0)