Chiko

Chiko is a free, open-source terminal interface for testing gRPC APIs. When a server supports reflection, it can discover and browse that server's gRPC endpoints. Chiko generates formatted request templates and supports Bearer tokens, custom headers, and metadata for requests. Users can save requests as bookmarks and replay them, and the project lists importing and exporting grpcurl commands among its completed features. SSL connection support is also listed in a release changelog. Installation options include Homebrew, Go install, source, and prebuilt releases. Chiko is licensed under MIT, and its Free plan is priced as free; no paid plans or usage limits are stated. The roadmap lists OAuth, API keys, and password protection for sensitive bookmarks as in progress, rather than completed features. The project is distributed as desktop software and hosted on GitHub. Its maker, Felix Angga, describes himself as a software engineer on his GitHub profile. The repository invites users to report issues, request features, improve documentation, and contribute code.

Chiko covers core gRPC request work with templates, bookmarks, and grpcurl command support. Its roadmap still lists OAuth, API keys, and protected bookmarks as in progress.

Chiko suits developers who want a terminal-based tool for testing gRPC APIs, especially when the server supports reflection. Its desktop distribution and installation options include Homebrew, Go install, source, and prebuilt releases.

Chiko is a terminal-based tool for developers who need to exercise gRPC services without leaving a command-line workflow. Its strongest fit is focused request testing and replay; teams that depend on OAuth, API keys, or protected bookmarks should look elsewhere for now.

Overview

Chiko combines service discovery, request setup, and saved calls in one terminal interface. It is a practical choice when a developer wants to explore RPCs and repeat requests without building a larger testing workflow around them. Discovery depends on server reflection, so services that do not support reflection cannot be browsed this way.

SSL connection support and grpcurl command import and export make Chiko relevant to developers whose gRPC work already includes those tools. Bearer tokens cover one common authorization method, but Chiko is not yet suited to authentication workflows that require OAuth or API keys.

Key features

Explore and prepare calls

For reflection-enabled servers, Chiko can discover and browse gRPC endpoints. It generates formatted request templates, giving users a starting structure for payloads instead of a blank request. Custom headers and metadata can be added when a service expects request-specific context.

Reuse and exchange requests

Bookmarks save requests for later replay, a useful shortcut for recurring checks or calls that need repeated setup. Importing and exporting grpcurl commands also gives users a way to move commands into or out of an existing grpcurl workflow.

Authentication and security boundaries

Bearer tokens are supported for request authorization. OAuth, API keys, and password protection for sensitive bookmarks remain in progress, so Chiko is a weaker fit for teams whose access controls or credential workflows depend on those capabilities.

Pricing

Chiko is free and open source under the MIT License. Its Free plan costs nothing, with no paid plans or usage limits stated. That makes it suitable for individual developers and teams seeking an open-source terminal tool without a subscription tier to weigh. The MIT license permits broad use, including commercial use, while retaining the license's terms.

Platforms

Chiko is a desktop deployment presented as a terminal interface. Installation options include Homebrew, Go install, building from source, and prebuilt releases, giving developers several ways to put it into a local workflow.

Who it's for

Chiko suits developers who prefer terminal tools, work with reflection-enabled gRPC services, and want to prepare, bookmark, and replay requests. It is also a reasonable option for users who already exchange grpcurl commands. It is less appropriate for teams that need OAuth, API-key authentication, or password-protected saved requests as part of their current process.

Pros and cons

• Pros: Reflection-based browsing, formatted request templates, custom metadata, and replayable bookmarks cover several core request-testing tasks in one terminal interface.
• Pros: grpcurl command import and export can fit into workflows already using grpcurl, and SSL support extends its connection options.
• Pros: Free, MIT-licensed software with multiple installation routes avoids a paid plan or a single required installation method.
• Cons: Endpoint browsing requires server reflection, limiting discovery on services that do not support it.
• Cons: Bearer tokens are supported, but OAuth, API keys, and protected bookmarks are still in progress.

Alternatives

For gRPC load testing rather than interactive request work, choose ghz, a free open-source load-testing CLI and Go package with a beta complementary web application. If you need unary RPC calls and can build from source, gRPC CLI is another free option for Linux, macOS, and Windows.

gRPC Swagger is a free, MIT-licensed option for users looking for a self-hosted web or API tool. For Go developers seeking gRPC testing utilities as a module, consider grpcmock-go. If you prefer a cross-platform product with a free individual plan and limited request history, Kreya offers that alternative, though it is not open source.

protoc-gen-doc is another free MIT-licensed project. For generating static documentation from a Protobuf descriptor file, sabledocs is a free open-source option that requires Python 3.11 or later. Bandura offers a free tier for personal and commercial use with no account, paid seats, or feature tiers; its commercial licence costs $59, paid once.

Browse more options in gRPC Tools.

Verdict

Choose Chiko if you want a free terminal tool for exploring reflection-enabled gRPC services and keeping repeatable requests close at hand. Its templates, bookmarks, and grpcurl support make the core request workflow compelling; look elsewhere if OAuth, API keys, or protected bookmarks are requirements rather than future possibilities.