Nouto
Your API collections belong in the repo, not in someone's cloud.
REST and gRPC client with YAML collections. VS Code extension and desktop app, sharing one core.
name: Get a user
method: GET
url: https://api.example.com/users/42
headers:
accept: application/jsonSend the request
What it does
Collections are plain YAML
Requests live next to the code they exercise. They diff cleanly, review like any other file, and merge without a proprietary export step.
REST and gRPC in one client
Same collection format, same environments, same editor, whichever protocol the service happens to speak.
Checked against your OpenAPI spec
Point Nouto at a spec and it flags requests that will fail before you send them.
Editor or desktop, one core
Run it as a VS Code extension or a standalone app. Both read the same files, so switching costs nothing.
Nothing is gated
No seat limits, no paid tier holding environments hostage, and no account required to open a collection.
A closer look
- A YAML collection open beside its response pane
- A gRPC call with its service definition loaded
- Environment variables resolved across a collection
Captures of these views are being prepared.
Freeopen source
Runs on vs code · windows · macos · linux.