Apache RocketMQ
Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance, and reliability. It provides trillion-level message capacity with rich message types including normal, transactional, delayed, and ordered messages.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Apache RocketMQ the way a machine reads it — 70 machine-readable artifacts across 4 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 — Apache RocketMQ scores 48.2/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). 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 Apache RocketMQ
Each block below is one kind of artifact we hold for Apache RocketMQ. 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 4
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.
Apache RocketMQ Brokers API
The Brokers API from Apache RocketMQ — 1 operation(s) for brokers.
Apache RocketMQ ConsumerGroups API
The ConsumerGroups API from Apache RocketMQ — 1 operation(s) for consumergroups.
Apache RocketMQ Messages API
The Messages API from Apache RocketMQ — 3 operation(s) for messages.
Apache RocketMQ Topics API
The Topics API from Apache RocketMQ — 2 operation(s) for topics.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apache Rocketmq Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Apache Rocketmq Finops
FINOPSFeatures 7
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.
High Throughput
Billion-level message throughput with low latency
Multiple Message Types
Normal, ordered, delayed, transactional, and batch messages
Message Filtering
Server-side tag and SQL expression filtering
Exactly-Once Semantics
Transactional messages for exactly-once delivery
Delayed Messages
Schedule messages with configurable delay levels
Dead Letter Queue
Automatic dead letter queue for failed messages
Message Tracing
End-to-end message tracing for debugging and monitoring
Scroll within the panel for all 7 ·
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.
Apache Rocketmq Context
JSON-LDSpectral Rules 2
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.
Apache RocketMQ API Rules
SPECTRALApache RocketMQ API Rules
SPECTRALJSON Schema 14
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.
AckRequest
JSON SCHEMABrokerList
JSON SCHEMABroker
JSON SCHEMAConsumerGroupList
JSON SCHEMAConsumerGroupRequest
JSON SCHEMAConsumerGroup
JSON SCHEMAMessageRequest
JSON SCHEMAMessage
JSON SCHEMAReceiveRequest
JSON SCHEMAReceiveResult
JSON SCHEMASendResult
JSON SCHEMATopicList
JSON SCHEMATopicRequest
JSON SCHEMATopic
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 14
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apache Rocketmq Ack Request Structure
JSON STRUCTUREApache Rocketmq Broker List Structure
JSON STRUCTUREApache Rocketmq Broker Structure
JSON STRUCTUREApache Rocketmq Consumer Group List Structure
JSON STRUCTUREApache Rocketmq Consumer Group Request Structure
JSON STRUCTUREApache Rocketmq Consumer Group Structure
JSON STRUCTUREApache Rocketmq Message Request Structure
JSON STRUCTUREApache Rocketmq Message Structure
JSON STRUCTUREApache Rocketmq Receive Request Structure
JSON STRUCTUREApache Rocketmq Receive Result Structure
JSON STRUCTUREApache Rocketmq Send Result Structure
JSON STRUCTUREApache Rocketmq Topic List Structure
JSON STRUCTUREApache Rocketmq Topic Request Structure
JSON STRUCTUREApache Rocketmq Topic Structure
JSON STRUCTUREScroll within the panel for all 14 ·
Examples 14
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 14 ·
Security Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
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.
Order Processing
Ensure ordered processing of e-commerce order events
Event-Driven Microservices
Decouple microservices with reliable asynchronous messaging
Log Aggregation
Aggregate application logs from distributed services
Financial Transactions
Reliable transactional messaging for financial systems
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Spring Boot
RocketMQ Spring Boot starter for easy integration
Apache Flink
Flink connector for stream processing from RocketMQ
Apache Spark
Spark Streaming connector for RocketMQ
Kubernetes
RocketMQ Operator for Kubernetes-native deployment
Resources
Every other property we hold for Apache RocketMQ — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/apache-rocketmq · machine-readable index on apis.io