google-aip
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · API-DESIGN · AIP · REST · GRPC · GOOGLE
What an agent uses it for
An agent designing a resource-oriented REST or gRPC API queries this for Google's API Improvement Proposals on naming, pagination, field masks, errors, and long-running operations.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/google-aip.jsonxerj corpus add --from ./google-aip.jsonxerj corpus index google-aip then xerj code google-aip "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: "google-aip", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| google.aip.dev | 615875bffc45 | CC-BY-4.0 | 806.4 KB / 162 files | LICENSE.md read directly (GitHub reports NOASSERTION): dual-licence: repository content CC-BY-4.0, code samples Apache-2.0, both allow-listed. Indexable value is the CC-BY-4.0 prose; attribute Google. ls-remote HEAD OK. |
806.4 KB across 162 files. Added 2026-10-13.
Rights
CC-BY-4.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.