Axon Framework
Axon Framework is a Java framework for building event-driven microservices using CQRS (Command Query Responsibility Segregation) and event sourcing patterns, providing the building blocks to implement scalable and maintainable distributed systems.
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 Axon Framework the way a machine reads it — 66 machine-readable artifacts across 9 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 — Axon Framework scores 57.4/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 Axon Framework
Each block below is one kind of artifact we hold for Axon Framework. 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 9
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.
Axon Framework Applications API
The Applications API from Axon Framework — 1 operation(s) for applications.
Axon Framework Cluster API
The Cluster API from Axon Framework — 2 operation(s) for cluster.
Axon Framework Commands API
The Commands API from Axon Framework — 1 operation(s) for commands.
Axon Framework Contexts API
The Contexts API from Axon Framework — 2 operation(s) for contexts.
Axon Framework Event Processors API
The Event Processors API from Axon Framework — 3 operation(s) for event processors.
Axon Framework Events API
The Events API from Axon Framework — 2 operation(s) for events.
Axon Framework Queries API
The Queries API from Axon Framework — 1 operation(s) for queries.
Axon Framework Snapshots API
The Snapshots API from Axon Framework — 1 operation(s) for snapshots.
Axon Framework Users API
The Users API from Axon Framework — 2 operation(s) for users.
Scroll within the panel for all 9 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Axon Server REST API
OPEN COLLECTIONPricing 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.
Axon Framework 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.
Axon Framework 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.
CQRS Pattern
Separate command and query models for scalable, maintainable architecture.
Event Sourcing
Store application state as a sequence of events for full audit trail and time-travel debugging.
Domain-Driven Design
First-class support for DDD patterns including aggregates, sagas, and bounded contexts.
Axon Server Integration
Zero-configuration event store and message router with Axon Server.
Distributed Systems Support
Built-in routing for commands, events, and queries across distributed services.
Spring Boot Integration
Seamless Spring Boot auto-configuration for rapid application development.
Testing Support
Built-in testing fixtures for validating aggregate behavior without infrastructure.
Saga Management
Manage long-running business processes with durable saga state.
Scroll within the panel for all 8 ·
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.
Axon Framework 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.
Axon Framework API Rules
SPECTRALAxon Framework API Rules
SPECTRALJSON Schema 10
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.
Application
JSON SCHEMAClusterNode
JSON SCHEMACommandHandler
JSON SCHEMAContext
JSON SCHEMACreateContextRequest
JSON SCHEMACreateUserRequest
JSON SCHEMAEvent
JSON SCHEMAEventProcessor
JSON SCHEMAQueryHandler
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 10 ·
JSON Structure 10
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.
Axon Application Structure
JSON STRUCTUREAxon Clusternode Structure
JSON STRUCTUREAxon Commandhandler Structure
JSON STRUCTUREAxon Context Structure
JSON STRUCTUREAxon Createcontextrequest Structure
JSON STRUCTUREAxon Createuserrequest Structure
JSON STRUCTUREAxon Event Structure
JSON STRUCTUREAxon Eventprocessor Structure
JSON STRUCTUREAxon Queryhandler Structure
JSON STRUCTUREAxon User Structure
JSON STRUCTUREScroll within the panel for all 10 ·
Examples 10
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.
Axon Application Example
EXAMPLEAxon Clusternode Example
EXAMPLEAxon Commandhandler Example
EXAMPLEAxon Context Example
EXAMPLEAxon Event Example
EXAMPLEAxon Eventprocessor Example
EXAMPLEAxon Queryhandler Example
EXAMPLEAxon User Example
EXAMPLEScroll within the panel for all 10 ·
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.
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 5
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 Architecture
Build event-driven microservices with reliable message routing.
Audit Trail
Maintain complete audit trails by storing all state changes as events.
Temporal Queries
Reconstruct system state at any point in time from the event store.
Collaborative Domains
Build complex collaborative domains with CQRS separation.
Workflow Automation
Automate multi-step business workflows with event-driven sagas.
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.
Spring Boot
Auto-configuration and starter dependency for Spring Boot integration.
Apache Kafka
Route events through Kafka as an alternative to Axon Server.
RabbitMQ
Route commands and events through AMQP with RabbitMQ extension.
JPA/Hibernate
Persist saga state and event-sourced entities with JPA.
Micrometer
Expose framework metrics via Micrometer for Prometheus and Grafana.
Resources
Every other property we hold for Axon Framework — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
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
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/axon-framework · machine-readable index on apis.io