Integrations

Architecture docs that stay in sync.

Generate services, messages and schemas from your specs, your schema registries, or straight from your code with the EventCatalog Agent, and keep them current on every change. Then add what no source can tell you: the domain, its language, who owns what and why. Your teams and your AI agents get the whole picture.

Explore spec integrations Connect your agents

Specs keep it current. Your teams add the context.

OpenAPI and AsyncAPI generate the parts of your architecture that change most, and keep them in sync. Specs can’t describe your domains, ubiquitous language or ownership, so you document those alongside, and your writing survives every regeneration.

AsyncAPI

Event-driven APIs

Your AsyncAPI files become services, channels and messages, with producers and consumers connected and a page for every message.

Read the AsyncAPI docs

orders-service.asyncapi.yml

asyncapi: 3.0.0

info:

title: Orders Service

channels:

orders.events: { bindings: kafka }

operations:

sendOrderCreated: { action: send }

receivePaymentTaken: { action: receive }

EventCatalog

Architecture Diagram

EventPaymentTaken

ServiceOrders Service

EventOrderCreated

Kafka channelorders.events

Documentation

EventOrderCreatedv1.2.0

ProducerOrders Service

Kafka channelorders.events

SchemaOrderCreated.avsc

OrderCreated.avscAvro

{
  "type": "record",
  "name": "OrderCreated",
  "fields": [
    { "name": "orderId", "type": "string" },
    { "name": "customerId", "type": "string" },
    { "name": "amount", "type": "double" },
    { "name": "currency", "type": "string" },
    { "name": "createdAt", "type": "timestamp-millis" }
  ]
}

OpenAPI

REST APIs

Your OpenAPI files become a documented service with its commands and queries, visualized, with the spec rendered alongside.

Read the OpenAPI docs

Schema registries

Confluent, Apicurio, GitHub and more

Schemas only tell half the story. Keep them where they live today, and let EventCatalog add the meaning: what each message is for and who depends on it.

Read the registry docs

Confluent Schema Registry

Apicurio Registry

GitHub

Your own registryvia the SDK

EventCatalog

Documentation

EventOrderCreatedv3

added in EventCatalog

Raised when a customer’s payment clears and the order is confirmed. Starts fulfilment and invoicing.

DomainOrders

OwnerOrders team

ConsumersBilling, Fulfilment

DecisionADR-012

OrderCreated.avscAvro · v3synced from your registry

{
  "type": "record",
  "name": "OrderCreated",
  "fields": [
    { "name": "orderId", "type": "string" },
    { "name": "customerId", "type": "string" },
    { "name": "amount", "type": "double" },
    { "name": "currency", "type": "string" },
    { "name": "createdAt", "type": "timestamp-millis" }
  ]
}

EventCatalog Agent

Code to docs, on every pull request

Write the code and the docs follow. On every pull request, the agent works out which docs your change affects, updates them, and opens a pull request to your catalog for you to review.

Read the Agent docs

orders-service#231Open

Publish OrderShipped when an order ships

src/shipping/ship-order.ts

+ await producer.send('orders.events', {+ type: 'OrderShipped',+ orderId, carrier, trackingId,+ });

EventCatalog Agent

Review the diff
Plan the impact
Update the docs
Lint and open PR

your-catalog#88Waiting for agent

+events/OrderShipped/index.mdxnew event
~services/OrdersService/index.mdxnow sends OrderShipped
~channels/orders.events/index.mdxnew message

Only the docs this change affects. You review and merge.

Sync from where they live

Point at a file, a URL or a schema registry, and regenerate from CI/CD whenever something changes.

Versioned with your specs

Each spec version becomes a catalog version, so history is never lost.

Your writing is kept

Context you add in markdown survives every regeneration.

Your architecture, available to every agent.

EventCatalog turns your architecture into a structured graph of domains, services, messages and owners. Agents read it to answer questions, and write to it to keep it current.

Works with

Claude

Claude Code

OpenAI

CursorVS CodeAny MCP client

Your agentconnected to EventCatalog MCP

›

›Ask about your architecture…scope: orders domain

Read your architecture