The AsyncAPI index has 3,664 event-driven specifications from 3,448 providers. AsyncAPI is the contract for the half of an integration that OpenAPI cannot describe: the channels you subscribe to, the messages that arrive, and the order you have to do things in. For agents this is becoming more important, because an agent waiting on an order fill or a shipment update needs to know what will be pushed to it, not only what it can request.
How it is distributed
96% of the providers with any AsyncAPI have exactly one document, usually a single webhook or WebSocket catalog. The next-deepest publishers after WhiteBIT and Wazo are Modulate and Benzinga with 7 each and Bullish with 6.
What a good one looks like
WhiteBIT, a crypto exchange, publishes one AsyncAPI 3.0 document per WebSocket channel. There are 9 public channels (depth, trades, kline, book ticker, last price) and 32 private channels covering balances, positions, borrows and every order type it accepts. Each document goes past the core specification. x-auth-required marks the private channels. x-rate-limits sets 1,000 connections per minute and 12,000 requests per 10 seconds. x-error-codes explains each failure: code 6 means the connection did not call authorize first, and code 1 means the market is not a _PERP futures market. The ADL quantile channel also says when to stop using it: for a one-time snapshot, call POST /api/v4/collateral-account/adl-quantile instead. A client can be written from that document alone, and so can an agent’s error handling.
The version split
| Declared version | Documents | Providers |
|---|---|---|
| 3.0.0 | 300 | 231 |
| 2.6.0 | 502 | 462 |
| 2.0.0 | 17 | |
| 3.1.0 | 1 (xquik) | |
| none recorded | 2,644 | 2,637 |
Version 2.6 still has more documents and providers than 3.0. Only one document in the catalog declares 3.1. Most records have no version in the index at all, which means the index cannot yet answer the most basic question a code generator asks.
What is ours to fix
52 records hold a probe note in the version field instead of a version. Examples include “published: False” with the URLs we tried for Airwallex, CrowdStrike, Snowflake and Redocly. Those notes are useful findings, because they record that a provider has no AsyncAPI and that we did not fabricate one. They belong in the coverage record, though, not in a field a client parses as a version string.
Takeaway
AsyncAPI coverage across the catalog is wide but shallow. Nearly every publisher has one document, and most of those documents carry no version we can read. WhiteBIT shows what full coverage looks like: one document per channel, with auth, limits and errors written into each one. Browse the index at asyncapi.apis.io.
Elsewhere: this story on Yawplet · a reader's take on Yarnhen. Yawplet and Yarnhen are agent-first sites where AI agents post.