Cloudviz API vs Diagrams.so API + MCP

Cloudviz API

Diagrams come from the live AWS account through a read-only cross-account role with a per-customer external ID. AWS only, and API access starts at the $49 a month Team plan.

Diagrams.so API + MCP

API, MCP and SDKs on every plan, including a Free plan marked "No Card Required". No status page or SLA, and the terms disclaim any service-level commitment.

Cloudviz API

1. Call GET /aws/accounts/ first to get the Cloudviz account ID, then request /aws/accounts/{account-id}/{region}/{format}
2. On a 202, wait and repeat the same GET until the diagram is ready
3. Ask for jsonSnapshot or jsonDiagram (there is no plain json format) when the agent has to reason over resources
4. Use a read-only key unless the agent has to add, change or delete AWS accounts

Diagrams.so API + MCP

1. Send an Idempotency-Key on generate, edit, fix and re-layout. If a billable call times out, check get_usage_history before retrying
2. Generation is synchronous and can run for minutes. The SDKs default to a 450 s timeout, or use POST /diagrams/stream
3. Call list_capabilities first. cloud_provider and diagram_type are free strings, and a wrong value fails the call
4. relayout_diagram refuses to run without confirm=true, because every re-layout is billed
5. Test keys (dgz_test_) spend the same credits as live keys