gateway-api
reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · INGRESS · GATEWAY · NETWORKING · SPEC · ROUTING
What an agent uses it for
An agent implementing ingress/gateway routing queries this for the Gateway API spec, conformance semantics, and resource model.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/gateway-api.jsonxerj corpus add --from ./gateway-api.jsonxerj corpus index gateway-api then xerj code gateway-api "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: "gateway-api", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| gateway-api | 0da5a10ebb0e | Apache-2.0 | 17.8 MB / 1,891 files | licence host-verified (ok-spdx): Apache-2.0 |
17.8 MB across 1,891 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.