​
Diagrams

A diagram is the core object. It has an id, a title, native draw.io XML (xml), a cloud_provider, a diagram_type, and metadata. You create one by generating from a prompt, importing a draw.io file, or forking a gallery template. Every other write operation takes a diagram id.

​
The generate, review, fix loop

1

Generate

Turn a prompt into a diagram.
2

Review

Read the Well-Architected warnings and score returned on the diagram.
3

Fix or edit

Apply a fix for a specific warning, or edit freely with a prompt.
4

Export

Download SVG on any plan, or native draw.io XML on Paid.

​
Plans

There are two plans, Free and Paid, and both are unlimited. Nothing is metered; there is only a per-minute rate limit. Paid adds two things: images without a watermark, and the editable draw.io file. On Free, replies carry xml: null and a link to a watermarked SVG instead. See Plans & pricing. New diagrams start private on every plan.

​
Sync vs async

Most operations return synchronously. Re-layout runs as an async job that you poll. See Async operations.

​
Output formats

On Paid, diagrams are returned as draw.io XML (editable at app.diagrams.net) and can be exported as SVG. On Free you get the SVG, with a watermark. See Export formats.

​
Idempotency

Send an Idempotency-Key header on create calls so a retried request never creates a duplicate. See Idempotency.