> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/api-inventory/concepts/grpc-api-coverage-with-akto.md).

# gRPC API Coverage with Akto

**Akto** enables you to test and secure your gRPC services with ease. gRPC is a high-performance framework that uses HTTP/2 and Protocol Buffers for fast, type-safe communication. With Akto, you can:

* Discover and visualize gRPC endpoints
* Run functional and security tests
* Identify misconfigurations and risks in real time

Akto decodes and presents gRPC traffic in a human-readable format, even when encrypted, to support thorough testing and analysis.

### What Do gRPC APIs Look Like?

gRPC APIs typically use `POST` requests and are structured as `/ServiceName/MethodName`. They use special headers and content types like `application/grpc-*`.

Here’s an example request captured by Akto:

<figure><img src="/files/bXLSAqlgkbDhANsoVvJK" alt=""><figcaption></figcaption></figure>

Despite being transmitted over HTTP/2 and often encrypted, Akto decodes the full gRPC request, including method names, headers, and payloads, to support deep inspection and automated testing.

> ✅ Akto reveals full gRPC payloads even if the connection is encrypted.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akto.io/api-inventory/concepts/grpc-api-coverage-with-akto.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.