Events
Event-driven APIs catalog. Documents the landscape of brokers, streaming platforms, schema registries, and the specifications that standardize how events are described, transported, and stored. "Events" is the broader category that contains webhooks (HTTP callbacks) as one delivery surface, alongside message brokers, log-based streaming platforms, and managed pub/sub services. The catalog aligns around CloudEvents (CNCF graduated, v1.0.2) as the spec for the event payload envelope and AsyncAPI as the spec for the event API surface (channels, operations, messages, servers), and covers the major open-source brokers (Apache Kafka, Apache Pulsar, NATS, Redpanda, IBM MQ), cloud-native managed buses (AWS EventBridge, Azure Event Grid, Google Cloud Pub/Sub, Confluent Cloud), schema registries (Confluent Schema Registry, Apicurio Registry), and streaming-analytics SaaS (Tinybird, Materialize). Wire-level protocols included are MQTT (OASIS), AMQP (OASIS / ISO 19464), and STOMP.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Events the way a machine reads it — 53 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Events scores 26.8/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Events
Each block below is one kind of artifact we hold for Events. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
CloudEvents
CNCF-graduated specification (graduated January 25, 2024) for describing event data in a common way. Defines a payload envelope with required attributes id, source, specversion,...
AsyncAPI
Linux Foundation-hosted specification for event-driven APIs. Describes servers, channels, operations, messages, schemas, and protocol bindings for Kafka, AMQP, MQTT, NATS, WebSo...
Apache Kafka
Open-source distributed event streaming platform governed by the Apache Software Foundation. Described as used by "thousands of companies for high-performance data pipelines, st...
Apache Pulsar
Open-source distributed messaging and streaming platform built for the cloud. Top-10 Apache Software Foundation project (740+ contributors, current version 4.2). Multi-tenant by...
NATS
CNCF incubating high-performance, lightweight messaging system designed for cloud, edge, and IoT. Supports pub/sub, request/reply, and queue groups over a text-based protocol. J...
Redpanda
Kafka API-compatible streaming data platform written in C++ (no JVM, no ZooKeeper). Self-described as an "Agentic Data Plane and Data Streaming platform for real-time performanc...
IBM MQ
Enterprise messaging middleware from IBM. Long the de facto standard for assured-once message delivery in regulated industries (banking, government). Exposes the MQI native API,...
AWS EventBridge
AWS serverless event router. "EventBridge is a serverless service that uses events to connect application components together, making it easier for you to build scalable event-d...
Azure Event Grid
Azure's "highly scalable and fully managed publish-subscribe service for message distribution." Supports both HTTP push/pull delivery and an MQTT v3.1.1 / v5.0 broker mode for I...
Google Cloud Pub/Sub
Google Cloud's asynchronous and scalable messaging service that decouples message producers from consumers with typical latencies around 100 ms. Uses per-message leasing (not pa...
Confluent Cloud
Commercial managed service from Confluent positioned as "the industry's only fully managed data streaming platform." Built on the Kora cloud-native Kafka engine. Tiers: Basic, S...
Confluent Schema Registry
Central repository with a RESTful interface for registering and evolving schemas in Avro, JSON Schema, and Protobuf. Enforces compatibility rules (backward, forward, full, trans...
Apicurio Registry
Open-source schema and API artifact registry backed by Red Hat (Apache 2.0). Stores OpenAPI, AsyncAPI, Avro, JSON Schema, Protobuf, Kafka Connect schemas, GraphQL SDL, WSDL, and...
Tinybird
Managed ClickHouse-based SaaS for real-time analytics on event data. Ingests events via an HTTP Events API (up to 1,000 req/s) plus connectors for Kafka, S3, GCS, BigQuery, Snow...
Materialize
Streaming SQL database based on incremental view maintenance. Continually ingests CDC from Postgres, Kafka, and other sources, then keeps SQL views up to date with minimal recom...
MQTT
OASIS standard messaging protocol for the Internet of Things. Lightweight publish/subscribe transport for remote, constrained devices. Current version is MQTT 5.0 (predecessors ...
AMQP
Advanced Message Queuing Protocol. AMQP 1.0 is both an OASIS standard and an International Standard (ISO/IEC 19464). Wire-level binary protocol defining nodes, links, sessions, ...
STOMP
Simple (or Streaming) Text Oriented Messaging Protocol. Lightweight, text-based wire protocol for message-oriented middleware. Widely used as an alternative front-end on brokers...
Scroll within the panel for all 18 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Events GraphQL API
GRAPHQLFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Pub Sub Messaging
Many-to-many fan-out where producers publish to a topic and any number of subscribers receive a copy. Core to MQTT, NATS, Google Pub/Sub, Kafka (consumer-group fan-out), and Eve...
Queue Messaging
Point-to-point work distribution where each message is consumed by exactly one worker. Native to IBM MQ, RabbitMQ (AMQP 0-9-1), Pulsar shared subscriptions, and NATS queue groups.
Log Based Streaming
Durable, ordered, partitioned commit log that consumers read by offset. Kafka and Redpanda are the canonical implementations; Pulsar and Pub/Sub Lite share many properties.
Schema Governance
Schema registries (Confluent, Apicurio) version event schemas and enforce compatibility rules so producers cannot break consumers.
CloudEvents Envelope
Standard required attributes (id, source, specversion, type) plus optional (datacontenttype, dataschema, subject, time) wrap any event payload, with bindings for HTTP, Kafka, AM...
AsyncAPI Description
AsyncAPI documents describe the channels, operations, messages, and bindings of an event-driven API the way OpenAPI describes a REST API.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Events Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Events API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 7 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Microservice Integration
Decoupling services so producers emit events without coupling to downstream consumers.
Change Data Capture
Replicating database changes (Postgres logical replication, MySQL binlog, MongoDB change streams) onto Kafka, Pulsar, or Materialize for downstream consumers.
IoT Telemetry
Constrained devices publishing readings over MQTT or NATS to cloud gateways such as Azure Event Grid or AWS IoT Core.
Real Time Analytics
Streaming events into ClickHouse-, Pinot-, or Druid-based platforms (Tinybird, Materialize) to power user-facing dashboards with sub-second freshness.
Event Sourcing
Storing every state change as an immutable event in a durable log (Kafka, Pulsar) so application state can be rebuilt by replay.
Webhook Delivery
HTTP-based fan-out from a SaaS to subscriber URLs. The narrowest slice of the event landscape; covered in detail in the api-evangelist webhooks topic repo.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
CloudEvents
Common envelope adopted across Azure Event Grid, Knative, GitHub Webhooks (via cloudevents-go binding), and most CNCF event-emitting projects.
AsyncAPI
API description format used by Postman, Microcks, Apicurio, and numerous broker dashboards to render an event API surface.
Kafka Protocol
De facto wire protocol; supported natively by Confluent Cloud, Redpanda, Aiven, and (via proxies) Azure Event Hubs and Pulsar.
MQTT
Native protocol for Azure Event Grid namespaces, AWS IoT Core, HiveMQ, EMQX, and Mosquitto.
Schema Registry
Confluent Schema Registry and Apicurio Registry plug into Kafka serializers/deserializers in every major language client.
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Open Source Brokers
Apache Kafka, Apache Pulsar, NATS, Redpanda Community Edition, and RabbitMQ cover most self-hosted deployments.
Managed Cloud Buses
AWS EventBridge, Azure Event Grid, and Google Cloud Pub/Sub provide serverless, pay-per-event delivery within their respective clouds.
Managed Streaming SaaS
Confluent Cloud, Redpanda Cloud, Aiven for Kafka, and Tinybird offer fully managed Kafka or ClickHouse with their own consoles, APIs, and SLAs.
Specification Stack
CloudEvents (envelope), AsyncAPI (API description), and JSON Schema / Avro / Protobuf (payload schema) compose into the standards layer that brokers and registries implement.
Resources
Every other property we hold for Events — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/events · machine-readable index on apis.io