googleapis
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · PROTOBUF · GRPC · AIP · RESOURCE-ORIENTED · GOOGLE-APIS
What an agent uses it for
An agent designing resource-oriented gRPC/REST APIs the Google way queries this for canonical service .proto definitions and the common google.api protos.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/googleapis.jsonxerj corpus add --from ./googleapis.jsonxerj corpus index googleapis then xerj code googleapis "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: "googleapis", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| googleapis | dfaf98d48d05 | Apache-2.0 | 76.7 MB / 8,564 files | licence host-verified (ok-spdx): Apache-2.0 |
76.7 MB across 8,564 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.