API Client Reborn
HTTP and gRPC, side by side
Build REST requests or call unary and streaming gRPC methods using reflection or local proto files.
Open-source desktop API client
Your APIs.
Your files.
Your workflow.
A lightweight, local-first client for HTTP and gRPC. Keep requests readable, version them with Git, and inspect streams without holding the whole response in memory.
Free and open source · macOS, Windows, and Linux · No account required
Local-firstYour workspace stays on your machine
Git-friendlyReadable request files, easy diffs
HTTP + gRPCOne focused desktop client
Open sourceMIT licensed and community-visible
Built for the everyday API loop
Powerful where it counts.
Out of your way everywhere else.
Send requests, inspect responses, and keep your work in the same project workflow as your code.
Requests that belong to your repo
Store collections as plain files, review changes in Git, and share them through the same workflow as your code.
Streams without the memory pileup
Inspect live events and streaming responses while response data is spooled to disk.
Environments and secrets
Import Postman environments, switch context as you work, and keep local secrets outside version control.
CLI when you need it
Copy requests as cURL or grpcurl, and export collections as portable shell scripts.
Fits your desktop
Use a native desktop app with a theme that follows your system or switches to light or dark.
Local by design
Your API workspace is a folder.
Requests, environments, and collections live as files you can inspect, back up, and version. Imported collection variables take priority over your selected environment and workspace values.
See the file formats
my-api-project/
├── environments/
│ ├── development.env.json
│ └── production.env.json
├── collections/
│ ├── users/list_users.curl
│ └── grpc/watch_events.grpc
└── history.json
├── environments/
│ ├── development.env.json
│ └── production.env.json
├── collections/
│ ├── users/list_users.curl
│ └── grpc/watch_events.grpc
└── history.json
Streaming support
Follow the stream.
Keep the app responsive.
Server-sent events, chunked HTTP, and gRPC server streams arrive incrementally. Full response data is spooled to disk while the interface keeps a bounded preview available.
Response stream● receiving
event: update · data: {"count": 1}
event: update · data: {"count": 2}
event: update · data: {"count": 3}
●Response is being written to disk · preview stays bounded
Open source · MIT
Bring your requests back to your workflow.
Download the latest release or browse the source, report an issue, and help shape what comes next.