api-linter
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · API-DESIGN · AIP · LINTER · PROTOBUF · GO
What an agent uses it for
An agent enforcing resource-oriented API conventions queries this for how AIP rules are implemented as lint checks over protobuf.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/api-linter.jsonxerj corpus add --from ./api-linter.jsonxerj corpus index api-linter then xerj code api-linter "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: "api-linter", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| api-linter | 836098d530b3 | Apache-2.0 | 2.7 MB / 1,325 files | licence host-verified (ok-spdx): Apache-2.0 |
2.7 MB across 1,325 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.