asyncapi-spec
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · ASYNCAPI · SPECIFICATION · KAFKA · MQTT · AMQP · WEBSOCKETS · EVENT-DRIVEN
What an agent uses it for
An agent working on event-driven or message-based API definitions queries this for the AsyncAPI specification's document structure, protocol bindings (Kafka/MQTT/AMQP/WebSocket), and message schema semantics.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/asyncapi-spec.jsonxerj corpus add --from ./asyncapi-spec.jsonxerj corpus index asyncapi-spec then xerj code asyncapi-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: "asyncapi-spec", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| spec | 1dd65fd2c1ed | Apache-2.0 | 1.7 MB / 103 files | LICENSE read via GitHub API: full Apache License 2.0 text confirmed (GitHub licensee also detects Apache-2.0); repo public, not archived, git ls-remote HEAD OK. Cite file:line when adapting. |
1.7 MB across 103 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.