FREE TOOLS
AsyncAPI Channel Inspector
Inspect declared channels, messages and operations in supported AsyncAPI documents.
AsyncAPI JSON
asyncapi-channel-inspector.json (complete report)
Browser only
Runs locally in your browser. Your files, pasted content and generated output are not uploaded. Reset clears this tool’s working data.
This tool needs JavaScript. If it does not load, refresh the page and try again.
How to use this tool
- Enter values using the examples, or choose a local file where requested. Follow the displayed supported input shapes and limits.
- Choose Calculate result and inspect the complete result.
- Download result to save the primary file. Where supplied, additional links save source files and the full JSON report. Reset restores examples and clears output.
Examples
AsyncAPI JSON: {
"asyncapi": "3.0.0",
"info": {
"title": "Demo",
"version": "1"
},
"channels": {
"signup": {
"address": "users/signedup",
"messages": {
"signedUp": {
"name": "UserSignedUp",
"payload": {
"type": "object"
}
}
}
}
},
"operations": {
"sendSignup": {
"action": "send",
"channel": {
"$ref": "#/channels/signup"
}
}
}
}
Limitations
- Local JSON declaration inventory for exactly AsyncAPI2.6.0 and3.0.0. Report channel addresses,message names (null when unnamed),and application send/receive operations. In2.6 retain publish/subscribe and optional operationId;publish means application receive. In3.0 absent/null addresses stay unknown;explicit operation message subsets are reported. Follow inspected local URI-fragment references only;Reference Object siblings are ignored,while2.6 channel-ref siblings refuse because their merge semantics are undefined. Apply versioned scalar trait precedence for name/operationId;2.6 message oneOf wrappers must be nonempty. Other metadata,payload schemas,bindings,servers,replies and unused components are opaque. This is not full document/schema validation,protocol certification or a broker connection. Root-channel and explicit message-subset references must use literal existing root-map pointers;no implicit intermediate dereferencing. No3.1 or external-reference retrieval. At most2000 channels,2000 operations,2000 projected message slots and2000 trait applications;refs4096 characters/40 hops/20000 lookup steps;1MiB projected strings and shared100000-character/20000-node/40-level input and4MiB report bounds.
- Text fields are limited to100,000 UTF16 units each and400,000 combined UTF8 bytes; file fields have their own displayed limits. Combined output is at most4MiB. Processing stops after30 seconds; tool-specific bounds may be tighter.
- Generated source is a downloadable result and is not executed here. Inspection does not establish remote behavior, trust or standards certification.