grpc-gateway
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · GRPC · REST · GATEWAY · HTTP-ANNOTATIONS · PROTOBUF
What an agent uses it for
An agent exposing gRPC services as REST/JSON queries this for the google.api.http annotation mapping and reverse-proxy generation.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/grpc-gateway.jsonxerj corpus add --from ./grpc-gateway.jsonxerj corpus index grpc-gateway then xerj code grpc-gateway "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "grpc-gateway", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| grpc-gateway | 14c1da7cb18e | BSD-3-Clause | 9.4 MB / 719 files | licence host-verified (ok-spdx): BSD-3-Clause |
9.4 MB across 719 files. Added 2026-10-13.
Rights
BSD-3-Clause. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.