Scalar Renders AsyncAPI Bindings and Adds an Opt-In Mermaid Plugin
Scalar's Oct. 16 API reference release shows AsyncAPI bindings and reply schemas and adds opt-in Mermaid diagrams. Oct. 12 made channel messages searchable.

Scalar’s API reference now displays AsyncAPI bindings for servers, channels, operations and messages. A new opt-in plugin draws Mermaid diagrams inside Markdown. Scalar’s release notes for @scalar/api-reference list the changes under version 1.75.0, dated Oct. 16.
Bindings, replies and tag filters arrive in 1.75.0
Version 1.75.0 shows bindings together with their version details for all four AsyncAPI levels: server, channel, operation and message. Operation replies now render expandable message schemas, channel links and dynamic address expressions. AsyncAPI tags can be filtered. Channel grouping and navigation anchors stay in place.
The Mermaid plugin adds interactive diagrams to Markdown with zoom controls and keyboard panning. It is opt-in. Existing references render as before.
Search also changed in the same release. It now covers response schema fields and nested objects, and ranks field names above prose.
Version 1.74.0 made channels searchable
Scalar’s Oct. 12 release, 1.74.0, extended search to AsyncAPI channels, operations, messages, parameters and nested payload fields. It documents every channel message, including those no operation references, with filters for server and protocol.
Sidebar tag groups and nested parent tags now start collapsed. They open when you navigate to a child page. On localhost, Generate SDK buttons appear in the developer tools, the client libraries list and request examples. The sidebar footer shows an Explore Scalar card with a demo booking dialog.
Key takeaways
- Scalar 1.75.0 (Oct. 16) shows AsyncAPI bindings, reply schemas and channel links.
- An opt-in Mermaid plugin adds zoomable diagrams to Markdown.
- Version 1.74.0 (Oct. 12) made AsyncAPI channels, messages and payload fields searchable.
- Generate SDK buttons and the Explore Scalar card appear on localhost only.
The take
We think the unreferenced-message fix in 1.74.0 is the change to check first. A reference that lists only messages an operation points to hides the rest of an event API. Readers will assume the hidden messages don’t exist. Open your own AsyncAPI document in Scalar and compare the message list with the source file. Then try the Mermaid plugin on one page before turning it on across a site. It is the only change here that alters existing pages once enabled.


