API Contracts
Attach API Contracts to Your Architecture Model

Attach OpenAPI, AsyncAPI, or GraphQL schemas directly to C4 containers and components. Keep API contracts versioned alongside your architecture model for complete documentation.

View pricing
API Contracts

Contracts

Define and visualize your API surface

Create
billing-apiHTTP
user-servicegRPC
graph-apiGraphQL
eventsAsync
billing-apiv2.1.0HTTP
GET/v1/invoices
POST/v1/invoices
GET/v1/invoices/{id}
DELETE/v1/invoices/{id}
The problem

Pain you know too well

These challenges compound over time. The longer they go unaddressed, the more they cost in engineering time and reliability.

API docs are separate from architecture

API contracts live in Swagger UI or Stoplight while architecture diagrams are somewhere else. No connection between the two.

Contract changes break consumers

Without visibility into which teams consume which APIs, contract changes cause unexpected breakages.

API docs go stale

OpenAPI specs get outdated when nobody links them to the architecture view of the system.

How it works

Up and running in a few steps

1

Attach contracts to C4 elements

Upload or paste OpenAPI, AsyncAPI, or GraphQL schemas and link them to the containers or components that implement them.

2

Version alongside architecture

API contracts are versioned with your C4 model. Architecture changes and API changes are tracked together.

3

Browse APIs in architecture context

Click any container to see its API contracts. Understand what it exposes and consumes in the context of the full architecture.

4

Query APIs via MCP

AI assistants can query API contracts through MCP tools. Ask 'What API does the user service expose?' and get the OpenAPI spec.

Capabilities

Everything this feature does for you

OpenAPI, AsyncAPI, GraphQL

Support for major API specification formats. Attach multiple contracts to any C4 element.

Architecture-Linked APIs

See APIs in the context of your C4 model. Understand which components produce and consume each API.

Versioned Contracts

API contracts are versioned with your architecture model through change request workflows.

AI-Queryable APIs

MCP tools let AI assistants access API contracts. 'Show me the payment API schema' returns the actual spec.

Use cases

Where teams use it

01

Microservice API Documentation

Attach OpenAPI specs to each microservice container. Teams can browse the architecture and find APIs instantly.

02

Event-Driven Architecture

Use AsyncAPI schemas to document event channels between containers. Visualize event flows alongside your C4 model.

03

API Governance

Track which containers expose APIs and ensure all public APIs have documented contracts.

Free plan forever

API contracts that live with your architecture

Attach OpenAPI, AsyncAPI, and GraphQL schemas to C4 elements. Version them with your architecture model.

  • No credit card
  • Set up in five minutes
  • Viewers are always free

API Contracts and Event Channels, Linked to C4

Document API contracts and event channels linked to your C4 architecture. Track specifications, versions, and relationships.

Attach API Contracts to Your Architecture Model

Attach OpenAPI, AsyncAPI, or GraphQL schemas directly to C4 containers and components. Keep API contracts versioned alongside your architecture model for complete documentation.

API Contract Management | Archyl

Attach OpenAPI, AsyncAPI, and GraphQL schemas to C4 model elements. Version API contracts alongside your architecture documentation.

API contract management, OpenAPI architecture, AsyncAPI C4 model, API documentation architecture, API contract tool

API docs are separate from architecture

API contracts live in Swagger UI or Stoplight while architecture diagrams are somewhere else. No connection between the two.

Contract changes break consumers

Without visibility into which teams consume which APIs, contract changes cause unexpected breakages.

OpenAPI specs get outdated when nobody links them to the architecture view of the system.

Attach contracts to C4 elements

Upload or paste OpenAPI, AsyncAPI, or GraphQL schemas and link them to the containers or components that implement them.

Version alongside architecture

API contracts are versioned with your C4 model. Architecture changes and API changes are tracked together.

Browse APIs in architecture context

Click any container to see its API contracts. Understand what it exposes and consumes in the context of the full architecture.

AI assistants can query API contracts through MCP tools. Ask 'What API does the user service expose?' and get the OpenAPI spec.

OpenAPI, AsyncAPI, GraphQL

Support for major API specification formats. Attach multiple contracts to any C4 element.

Architecture-Linked APIs

See APIs in the context of your C4 model. Understand which components produce and consume each API.

API contracts are versioned with your architecture model through change request workflows.

MCP tools let AI assistants access API contracts. 'Show me the payment API schema' returns the actual spec.

Microservice API Documentation

Attach OpenAPI specs to each microservice container. Teams can browse the architecture and find APIs instantly.

Event-Driven Architecture

Use AsyncAPI schemas to document event channels between containers. Visualize event flows alongside your C4 model.

Track which containers expose APIs and ensure all public APIs have documented contracts.

API contracts that live with your architecture

Attach OpenAPI, AsyncAPI, and GraphQL schemas to C4 elements. Version them with your architecture model.