Free and Paid both get unlimited diagrams and edits. Nothing is metered; the one limit is a per-minute rate limit. Connect a client (MCP server or an SDK) or create an API key for raw HTTP. Both take about a minute in the Quickstart.

​
Build diagrams into your product

Diagrams.so turns a natural-language prompt, or an agent tool call, into a real, editable cloud-architecture diagram in native draw.io XML and SVG, with a Well-Architected review you can act on. Reach it three ways:

REST API

Call the API from any language to generate, edit, fix, and export diagrams.

MCP server

Let Claude, Cursor, or VS Code create and iterate diagrams in-loop.

SDKs

Typed Python and TypeScript clients over the same REST API.

​
Your first diagram in under 5 minutes

1

Connect a client, or get an API key

Connect the MCP server or an SDK once: enter your email, we email a one-time code, then sign in in the browser that opens, enter the code, and press Approve:
Prefer raw HTTP? Create a key at Settings → API Keys → Create key on diagrams.so. It is shown once, prefixed dgz_live_ (live) or dgz_test_ (test).
2

Make a call

3

Open the result

The response includes the diagram id and any Well-Architected warnings. On Paid it also carries the draw.io XML: open it at app.diagrams.net. On Free, xml is null and export_url points at a watermarked SVG. See Plans & pricing.

​
What you can build

Docs that never drift

Regenerate architecture diagrams from your infra description in CI, so docs stay current.

Agent-native diagrams

Let an AI agent draw, review, and fix a diagram as part of a larger task via MCP.

Well-Architected reviews

Surface warnings on a design and apply fixes programmatically.

Import and remix

Bring an existing draw.io file in and edit it with a prompt. Export it as SVG, or as draw.io on Paid.

​
Next steps

Quickstart

The full first-call walkthrough.

Authentication

Keys, scopes, and test mode.

API reference

Every endpoint.