msft-api-guidelines
reference corpus · status live · category GOOD (Design guidance & exemplars) · lane A · refresh pinned
What an agent uses it for
an agent designing a REST surface queries this for the naming/paging/versioning/error rules with examples
Use it
xerj corpus add --from https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/msft-api-guidelines.jsonxerj corpus index msft-api-guidelines → xerj code msft-api-guidelines "your question"Sources & pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| msft-api-guidelines | a7022a299442… | CC-BY-4.0 | 611.5 KB / 42 files | license.txt (lowercase) at pin: CC-BY-4.0; the profiler's uppercase-only name list missed it — name list fixed. | profiler evidence: PROFILER 2026-10-02T00:49:45Z trees-only — files=42; backlog hint: verify at pin (CC-BY reported); api licence: unknown; evidence: NO TOP-LEVEL LICENCE FILE FOUND — investigate before review |
611.5 KB across 42 files · added 2026-10-02
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.