json-api-spec
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · JSON-API · REST · SPECIFICATION · JSON
What an agent uses it for
An agent building a JSON REST API queries this for the JSON:API specification's document structure, resource relationships, includes, and query-parameter conventions.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/json-api-spec.jsonxerj corpus add --from ./json-api-spec.jsonxerj corpus index json-api-spec then xerj code json-api-spec "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: "json-api-spec", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| json-api | bde79ceb9e27 | CC0-1.0 | 2.0 MB / 597 files | LICENSE read via GitHub API: CC0 1.0 Universal text confirmed (GitHub detects CC0-1.0); public-domain dedication, no attribution legally required (courtesy credit advised). Default branch gh-pages; ls-remote HEAD OK. |
2.0 MB across 597 files. Added 2026-10-13.
Rights
CC0-1.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.