Apache EventMesh

Apache EventMesh is a dynamic event-driven application runtime used to decouple the application and backend middleware layer, providing a serverless platform for building distributed event-driven architectures with support for CloudEvents and multiple messaging protocols including HTTP, TCP, and gRPC.

Apache EventMesh publishes 7 APIs on the APIs.io network, including Messaging API, Client API, Event API, and 4 more. Tagged areas include Apache, CloudEvents, Event-Driven, Messaging, and Open-Source.

The Apache EventMesh catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 3 Spectral governance rulesets.

Apache EventMesh’s developer surface includes documentation, getting-started guide, engineering blog, support, and 12 more developer resources.

🌐 Visit website 📡 Source on GitHub

33.7/100 thin ▬ flat Agent 18/100 agent aware self hosted · Apache-2.0 Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessFreemium

1 APIs 7 Features 4 Use Cases

Apache CloudEvents Event-Driven Messaging Open-Source Pub-Sub Serverless

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 33.7/100 · thin

Contract Quality 11.5 / 20

Developer Ergonomics 2.7 / 16

Access Clarity 2.5 / 16

Operational Transparency 2.7 / 10

Contract Governance 2.8 / 10

Discoverability 4.7 / 8

Open Source Surface 4.0 / 10

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 18/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 80 points between them, because the conditional facet above carries the other 20. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 80% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/apache-event-mesh: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Apache EventMesh Messaging API

Event-driven messaging via TCP, HTTP, and gRPC protocols. Events follow the CloudEvents specification. Supports pub-sub, request-reply, and broadcast messaging patterns.

Apache EventMesh Client API

The Client API from Apache EventMesh — 1 operation(s) for client.

Apache EventMesh Event API

The Event API from Apache EventMesh — 2 operation(s) for event.

Apache EventMesh Monitoring API

The Monitoring API from Apache EventMesh — 2 operation(s) for monitoring.

Apache EventMesh Registry API

The Registry API from Apache EventMesh — 1 operation(s) for registry.

Apache EventMesh Subscription API

The Subscription API from Apache EventMesh — 1 operation(s) for subscription.

Apache EventMesh Topic API

The Topic API from Apache EventMesh — 3 operation(s) for topic.

Scroll for all 7

Open Collections 8

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Apache EventMesh Admin Client API

OPEN COLLECTION

Apache EventMesh Admin Client Event API

OPEN COLLECTION

Apache EventMesh Admin Client Monitoring API

OPEN COLLECTION

Apache EventMesh Admin Client Registry API

OPEN COLLECTION

Apache EventMesh Admin Client Subscription API

OPEN COLLECTION

Apache EventMesh Admin Client Topic API

OPEN COLLECTION

Apache EventMesh Admin API

OPEN COLLECTION

Scroll for all 8

Pricing Plans 1

Published pricing tiers and plan structures.

Apache Event Mesh Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Apache Event Mesh Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Apache Event Mesh Finops

FINOPS

Features 7

Notable capabilities this provider offers.

CloudEvents Support

Native CloudEvents specification support for standardized event envelopes across all messaging protocols.

Multi-Protocol Messaging

Support for HTTP, TCP, and gRPC messaging protocols enabling flexible client connectivity.

Pub-Sub Messaging

Publish-subscribe messaging pattern with topic-based routing for event-driven architectures.

Request-Reply Pattern

Synchronous request-reply messaging over asynchronous infrastructure for RPC-style interactions.

Event Store

Durable event storage with replay capability for reliable event delivery and audit trails.

Workflow Orchestration

Event-driven workflow engine for coordinating distributed business processes and sagas.

Multi-Runtime Support

Pluggable connector model supporting Kafka, RocketMQ, Pulsar, and other messaging backends.

Scroll for all 7

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Apache EventMesh Messaging API

Apache EventMesh provides event-driven messaging via multiple protocols including TCP, HTTP, and gRPC. Events follow the CloudEvents specification. EventMesh decouples event pro...

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Apache Event Mesh Admin Context

5 classes · 21 properties

JSON-LD

Spectral Rules 3

Spectral governance rulesets for linting and validating these APIs.

Apache EventMesh API Rules

2 rules · 2 warnings

SPECTRAL

Apache EventMesh API Rules

5 rules · 4 warnings 1 info

SPECTRAL

Apache EventMesh API Rules

14 rules · 4 errors 9 warnings 1 info

SPECTRAL

JSON Schema 5

Standalone JSON Schema definitions for this provider's data models.

CloudEvents v1.0

10 properties

JSON SCHEMA

ApiResponse

2 properties

JSON SCHEMA

Client

8 properties

JSON SCHEMA

CloudEvent

10 properties

JSON SCHEMA

Subscription

4 properties

JSON SCHEMA

JSON Structure 4

JSON Structure definitions describing this provider's data shapes.

Eventmesh Admin Api Response Structure

2 properties

JSON STRUCTURE

Eventmesh Admin Client Structure

8 properties

JSON STRUCTURE

Eventmesh Admin Cloud Event Structure

10 properties

JSON STRUCTURE

Eventmesh Admin Subscription Structure

4 properties

JSON STRUCTURE

Examples 4

Example request and response payloads for these APIs.

Eventmesh Admin Api Response Example

2 fields

EXAMPLE

Eventmesh Admin Client Example

8 fields

EXAMPLE

Eventmesh Admin Cloud Event Example

10 fields

EXAMPLE

Eventmesh Admin Subscription Example

4 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Apache Event Mesh Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Apache Event Mesh Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Apache Event Mesh Agentic Access

10 operations · 4 acting

AGENTIC

Use Cases 4

What developers build with this provider.

Microservices Decoupling

Decouple microservices through asynchronous event-driven communication reducing direct service dependencies.

Event Streaming Pipelines

Build scalable event streaming pipelines with durable delivery and replay capabilities.

Distributed Workflows

Orchestrate distributed business processes using event-driven saga and choreography patterns.

IoT Event Ingestion

Ingest and process high-volume IoT device events through standardized CloudEvents format.

Integrations 4

Pre-built integrations with other platforms and tools.

Apache Kafka

Kafka connector for event streaming with durable storage and consumer groups.

Apache RocketMQ

RocketMQ connector for high-throughput message queueing and topic management.

Apache Pulsar

Pulsar connector for multi-tenant event streaming with geo-replication.

Kubernetes

Cloud-native deployment on Kubernetes with operator support for cluster management.

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

SpectralRules

SpectralRules

Vocabulary

Vocabulary

Build 3

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

Access & Security 2

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

IssueTracker

IssueTracker

Releases

Releases

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

License

License

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: apache-event-mesh
name: Apache EventMesh
description: Apache EventMesh is a dynamic event-driven application runtime used to decouple the application and backend middleware
  layer, providing a serverless platform for building distributed event-driven architectures with support for CloudEvents
  and multiple messaging protocols including HTTP, TCP, and gRPC.
type: Index
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/apache-event-mesh.png
tags:
- Apache
- CloudEvents
- Event-Driven
- Messaging
- Open-Source
- Pub-Sub
- Serverless
tags_raw:
- Apache
- CloudEvents
- Event-Driven
- Messaging
- Open Source
- Pub-Sub
- Serverless
url: https://raw.githubusercontent.com/api-evangelist/apache-event-mesh/refs/heads/main/apis.yml
created: '2026-03-26'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: apache-event-mesh:eventmesh-messaging-api
  name: Apache EventMesh Messaging API
  description: Event-driven messaging via TCP, HTTP, and gRPC protocols. Events follow the CloudEvents specification. Supports
    pub-sub, request-reply, and broadcast messaging patterns.
  humanURL: https://eventmesh.apache.org/docs/sdk-java/tcp-sdk-usage
  tags:
  - CloudEvents
  - Event-Driven
  - Messaging
  - Pub-Sub
  properties:
  - type: Documentation
    url: https://eventmesh.apache.org/docs/sdk-java/tcp-sdk-usage
  - type: AsyncAPI
    url: asyncapi/eventmesh-messaging.yml
- aid: apache-event-mesh:apache-event-mesh-client-api
  name: Apache EventMesh Client API
  description: The Client API from Apache EventMesh — 1 operation(s) for client.
  humanURL: https://eventmesh.apache.org/docs/instruction/quickstart
  baseURL: http://localhost:10106
  tags:
  - Clients
  tags_raw:
  - Client
  properties:
  - type: OpenAPI
    url: openapi/apache-event-mesh-client-api-openapi.yml
  - type: Documentation
    url: https://eventmesh.apache.org/docs/introduction
  - type: JSONSchema
    url: json-schema/eventmesh-admin-cloud-event-schema.json
  - type: JSONLD
    url: json-ld/apache-event-mesh-admin-context.jsonld
- aid: apache-event-mesh:apache-event-mesh-event-api
  name: Apache EventMesh Event API
  description: The Event API from Apache EventMesh — 2 operation(s) for event.
  humanURL: https://eventmesh.apache.org/docs/instruction/quickstart
  baseURL: http://localhost:10106
  tags:
  - Event
  properties:
  - type: OpenAPI
    url: openapi/apache-event-mesh-event-api-openapi.yml
  - type: Documentation
    url: https://eventmesh.apache.org/docs/introduction
  - type: JSONSchema
    url: json-schema/eventmesh-admin-cloud-event-schema.json
  - type: JSONLD
    url: json-ld/apache-event-mesh-admin-context.jsonld
- aid: apache-event-mesh:apache-event-mesh-monitoring-api
  name: Apache EventMesh Monitoring API
  description: The Monitoring API from Apache EventMesh — 2 operation(s) for monitoring.
  humanURL: https://eventmesh.apache.org/docs/instruction/quickstart
  baseURL: http://localhost:10106
  tags:
  - Monitoring
  properties:
  - type: OpenAPI
    url: openapi/apache-event-mesh-monitoring-api-openapi.yml
  - type: Documentation
    url: https://eventmesh.apache.org/docs/introduction
  - type: JSONSchema
    url: json-schema/eventmesh-admin-cloud-event-schema.json
  - type: JSONLD
    url: json-ld/apache-event-mesh-admin-context.jsonld
- aid: apache-event-mesh:apache-event-mesh-registry-api
  name: Apache EventMesh Registry API
  description: The Registry API from Apache EventMesh — 1 operation(s) for registry.
  humanURL: https://eventmesh.apache.org/docs/instruction/quickstart
  baseURL: http://localhost:10106
  tags:
  - Registry
  properties:
  - type: OpenAPI
    url: openapi/apache-event-mesh-registry-api-openapi.yml
  - type: Documentation
    url: https://eventmesh.apache.org/docs/introduction
  - type: JSONSchema
    url: json-schema/eventmesh-admin-cloud-event-schema.json
  - type: JSONLD
    url: json-ld/apache-event-mesh-admin-context.jsonld
- aid: apache-event-mesh:apache-event-mesh-subscription-api
  name: Apache EventMesh Subscription API
  description: The Subscription API from Apache EventMesh — 1 operation(s) for subscription.
  humanURL: https://eventmesh.apache.org/docs/instruction/quickstart
  baseURL: http://localhost:10106
  tags:
  - Subscription
  properties:
  - type: OpenAPI
    url: openapi/apache-event-mesh-subscription-api-openapi.yml
  - type: Documentation
    url: https://eventmesh.apache.org/docs/introduction
  - type: JSONSchema
    url: json-schema/eventmesh-admin-cloud-event-schema.json
  - type: JSONLD
    url: json-ld/apache-event-mesh-admin-context.jsonld
- aid: apache-event-mesh:apache-event-mesh-topic-api
  name: Apache EventMesh Topic API
  description: The Topic API from Apache EventMesh — 3 operation(s) for topic.
  humanURL: https://eventmesh.apache.org/docs/instruction/quickstart
  baseURL: http://localhost:10106
  tags:
  - Topic
  properties:
  - type: OpenAPI
    url: openapi/apache-event-mesh-topic-api-openapi.yml
  - type: Documentation
    url: https://eventmesh.apache.org/docs/introduction
  - type: JSONSchema
    url: json-schema/eventmesh-admin-cloud-event-schema.json
  - type: JSONLD
    url: json-ld/apache-event-mesh-admin-context.jsonld
common:
- type: Website
  url: https://www.apache.org/
- type: IssueTracker
  url: https://github.com/apache/eventmesh/issues
- type: Releases
  url: https://github.com/apache/eventmesh/releases
- type: CodeOfConduct
  url: https://github.com/apache/.github/blob/main/.github/CODE_OF_CONDUCT.md
- type: License
  name: Apache-2.0
  url: https://github.com/apache/eventmesh/blob/develop/LICENSE
- type: AgenticAccess
  url: agentic-access/apache-event-mesh-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/apache-event-mesh-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/apache-event-mesh-domain-security.yml
- type: Documentation
  url: https://eventmesh.apache.org/docs/introduction
- type: GettingStarted
  url: https://eventmesh.apache.org/docs/instruction/quickstart
- type: GitHubOrganization
  url: https://github.com/apache
- type: GitHubRepository
  url: https://github.com/apache/eventmesh
- type: Blog
  url: https://eventmesh.apache.org/blog
- type: Support
  url: https://eventmesh.apache.org/community
- type: SpectralRules
  url: rules/apache-event-mesh-spectral-rules.yml
- type: Vocabulary
  url: vocabulary/apache-event-mesh-vocabulary.yaml
- type: Features
  data:
  - name: CloudEvents Support
    description: Native CloudEvents specification support for standardized event envelopes across all messaging protocols.
  - name: Multi-Protocol Messaging
    description: Support for HTTP, TCP, and gRPC messaging protocols enabling flexible client connectivity.
  - name: Pub-Sub Messaging
    description: Publish-subscribe messaging pattern with topic-based routing for event-driven architectures.
  - name: Request-Reply Pattern
    description: Synchronous request-reply messaging over asynchronous infrastructure for RPC-style interactions.
  - name: Event Store
    description: Durable event storage with replay capability for reliable event delivery and audit trails.
  - name: Workflow Orchestration
    description: Event-driven workflow engine for coordinating distributed business processes and sagas.
  - name: Multi-Runtime Support
    description: Pluggable connector model supporting Kafka, RocketMQ, Pulsar, and other messaging backends.
- type: UseCases
  data:
  - name: Microservices Decoupling
    description: Decouple microservices through asynchronous event-driven communication reducing direct service dependencies.
  - name: Event Streaming Pipelines
    description: Build scalable event streaming pipelines with durable delivery and replay capabilities.
  - name: Distributed Workflows
    description: Orchestrate distributed business processes using event-driven saga and choreography patterns.
  - name: IoT Event Ingestion
    description: Ingest and process high-volume IoT device events through standardized CloudEvents format.
- type: Integrations
  data:
  - name: Apache Kafka
    description: Kafka connector for event streaming with durable storage and consumer groups.
  - name: Apache RocketMQ
    description: RocketMQ connector for high-throughput message queueing and topic management.
  - name: Apache Pulsar
    description: Pulsar connector for multi-tenant event streaming with geo-replication.
  - name: Kubernetes
    description: Cloud-native deployment on Kubernetes with operator support for cluster management.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/apache-event-mesh"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/apache-event-mesh/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/apache-event-mesh/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.