connect-protocol
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · GRPC · RPC · PROTOBUF · HTTP · CONNECT
What an agent uses it for
An agent implementing a protobuf RPC protocol over HTTP/1.1 and HTTP/2 with gRPC compatibility queries this for the Connect protocol specification and docs.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/connect-protocol.jsonxerj corpus add --from ./connect-protocol.jsonxerj corpus index connect-protocol then xerj code connect-protocol "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: "connect-protocol", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| connectrpc.com | 088d64e13216 | Apache-2.0 | 3.0 MB / 177 files | licence host-verified (ok-spdx): Apache-2.0 |
3.0 MB across 177 files. Added 2026-10-13.
Rights
Apache-2.0. 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.