AMQP
AMQP (Advanced Message Queuing Protocol) is an open standard for message-oriented middleware governed by OASIS and standardized as ISO/IEC 19464. AMQP 1.0 enables interoperable, asynchronous communication between applications across different platforms and vendors. It defines a wire-level protocol supporting reliable queuing, flexible routing, publish/subscribe, and request/reply messaging patterns. Major implementations include Apache ActiveMQ/Artemis, RabbitMQ, Azure Service Bus, Red Hat AMQ, and Apache Qpid.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles AMQP the way a machine reads it — 50 machine-readable artifacts across 1 API, 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 — AMQP scores 29.1/100 (thin), with a separate agent-readiness read of 17/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from AMQP's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amqp/"
title="AMQP on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amqp.svg"
alt="AMQP Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/amqp/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amqp/"
title="AMQP on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amqp/card.svg"
alt="AMQP Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile AMQP
Each block below is one kind of artifact we hold for AMQP. 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 1
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.
AMQP Messaging API
AsyncAPI specification for AMQP messaging patterns including publish/subscribe, request/reply, and point-to-point messaging via exchanges, queues, and bindings.
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Amqp Plans Pricing
PLANSRate 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.
Amqp 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.
Amqp Finops
FINOPSFeatures 8
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.
Reliable Messaging
Guaranteed delivery with acknowledgment and persistence support.
Flexible Routing
Exchange types (direct, fanout, topic, headers) for flexible message routing.
Publish/Subscribe
Fan-out delivery to multiple consumers via topic and fanout exchanges.
Request/Reply
Synchronous RPC patterns over asynchronous messaging infrastructure.
Transaction Support
Transactional message publishing and acknowledgment for data consistency.
Security
SASL authentication and TLS encryption for secure message transport.
Flow Control
Credit-based flow control preventing consumer overload (AMQP 1.0).
Multi-Vendor Interoperability
Wire-level protocol interoperability across different broker implementations.
Scroll within the panel for all 8 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
AMQP Messaging API
AsyncAPI specification for AMQP (Advanced Message Queuing Protocol) messaging patterns including publish/subscribe, request/reply, and point-to-point messaging. AMQP 0-9-1 defin...
ASYNCAPISemantic Vocabularies 6
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.
Amqp Amqp Binding Context
JSON-LDAmqp Amqp Exchange Context
JSON-LDAmqp Amqp Message Context
JSON-LDAmqp Amqp Queue Context
JSON-LDAmqp Context
JSON-LDSpectral Rules 3
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.
JSON Schema 5
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.
AMQP Binding
JSON SCHEMAAMQP Exchange
JSON SCHEMAAMQP Message Properties
JSON SCHEMAAMQP Message
JSON SCHEMAAMQP Queue
JSON SCHEMAJSON Structure 5
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.
Amqp Binding Structure
JSON STRUCTUREAmqp Exchange Structure
JSON STRUCTUREAmqp Message Properties Structure
JSON STRUCTUREAmqp Message Structure
JSON STRUCTUREAmqp Queue Structure
JSON STRUCTUREExamples 5
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.
Amqp Binding Example
EXAMPLEAmqp Exchange Example
EXAMPLEAmqp Message Example
EXAMPLEAmqp Queue Example
EXAMPLESecurity 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.
Microservices Communication
Decoupled inter-service messaging in microservices architectures.
Event Streaming
Event-driven architecture with durable, ordered event delivery.
Task Queues
Distributed work queues for background job processing.
IoT Messaging
Device-to-cloud and cloud-to-device messaging for IoT platforms.
Financial Messaging
High-reliability financial transaction messaging with guaranteed delivery.
Log Aggregation
Centralized log collection and routing from distributed systems.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
RabbitMQ
Popular AMQP 0-9-1 compliant broker with extensive plugin ecosystem.
Apache ActiveMQ
Java-based message broker supporting AMQP 1.0 and multiple protocols.
Azure Service Bus
Microsoft's cloud messaging service with AMQP 1.0 support.
Apache Qpid
AMQP 1.0 implementation with broker and client library support.
Red Hat AMQ
Enterprise messaging platform based on ActiveMQ Artemis with AMQP 1.0.
Solace PubSub+
Enterprise event broker supporting AMQP 1.0 among multiple protocols.
Resources
Every other property we hold for AMQP — 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
Documentation 6
Reference material describing how the API behaves
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amqp · machine-readable index on apis.io
This is an independent, third-party profile of AMQP, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.