Head to head · Diagram creation · October 2026 research run

Cloudviz API vs Eraser API + MCP

Eraser API + MCP scores 36.2 (F) on agent readiness against Cloudviz API's 25.7 (F), and leads in 4 of 7 scored categories. Cloudviz API leads on reliability. Both do diagram creation.

Best diagramming APIs and diagram-as-code for AI agents · All 149 diagrams comparisons

Which one, for what

Cloudviz API F

Best for Documenting what already runs in AWS, for example regenerating a diagram after each deploy and posting it to Confluence or Slack.

Ahead on

  • Reliability, 20 against 15

Watch for

AWS only, and API access starts at the $49 a month Team plan

Eraser API + MCP F

Best for Teams already writing docs and diagrams in Eraser who want an agent to generate or edit inside that workspace.

Ahead on

  • Schema & documentation, 37 against 8
  • Security & auth, 57 against 35
  • Payments & pricing, 53 against 30

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

No status page, rate limits, SLA or changelog

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Eraser API + MCP +29

Cloudviz API 8

The API reference at cloudviz.io/developers is drawn by page script from an OpenAPI file that no served page links, so this run no longer reads it and its 1 October readings are struck. No machine-readable contract can be read (0). No llms.txt, the URL returns 404 on 10 November 2026 (0). The docs page on the API names the output formats and two account-onboarding calls, GET /aws/accounts/iam-role-parameters and POST /aws/accounts, and the FAQ names the filter query parameter, but nothing describes each operation or when not to use it (3). No typed parameters or enums on any served page (0). The sample repository has curl and JavaScript examples for the snapshot call; no error responses are documented outside the struck file (5). No changelog and no API version on a served page (0).

Eraser API + MCP 37

No downloadable OpenAPI file. Endpoints are documented one page at a time on docs.eraser.io, which no longer runs on readme.io, and the hosted MCP's tool definitions are closed source. Typed schemas in the local server's source (zod, at the 0.7.0 tag) aren't a published contract, and the protocol alone shows no schema of Eraser's, so the contract line has no evidence (0 of 25). llms.txt with a .md twin for each page (10). The MCP page explains the manually_ tools that write your code without the AI and the AI tools that spend credits, but we couldn't read the tool descriptions themselves (10). Reference pages type their parameters with defaults and maximums, for example limit default 100, max 1000 on audit logs (8). Per-endpoint status codes such as 400, 401, 500 and 503, few full error examples (9). No changelog (eraser.io/changelog returns 404) and no API version in the path (0). 0 + 10 + 10 + 8 + 9 + 0 = 37.

Payments & pricing Eraser API + MCP +23

Cloudviz API 30

No x402, MPP or L402 (0). Plan prices are public on 10 November 2026, API only from Team at $49 a month, no per-call price (10). A 10-day trial for "every new subscriber". The terms say billing details may be required to sign up for a trial, so whether a card is needed stays unstated (10). A person signs up in the browser and connects AWS by hand (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Eraser API + MCP 53

No x402, MPP or L402 (0). Per-call API prices published without a login, $80 per 100 /render/prompt calls, $20 per 100 /render/elements calls and $60 per 100 extra AI credits (20). A $0 "free forever" plan with 3 files and 3 AI credits that works with the MCP server. The page doesn't say whether a card is asked for (15). Signup and OAuth consent need a person, and API tokens need a paid team (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Security & auth Eraser API + MCP +22

Cloudviz API 35

The API reference at cloudviz.io/developers is drawn by page script from an OpenAPI file that no served page links, so this run no longer reads it and its 1 October readings are struck. The samples send one API key in the x-api-key header. The 30 September listing facts on read-only and read-and-write keys trace to the struck reference, and no served page documents key scopes or revocation, so the line reads as one key (10). AWS access is a cross-account role with a per-customer external ID, and the security page recommends the AWS ReadOnlyAccess policy or a stricter custom one; no confirmation step for account deletion is documented (12). Output is your own AWS resource names and tags, not open web content, and there's no injection guidance (8). No audit log for API calls found (0). A security page asks for bug reports at security@cloudviz.io with no acknowledgement time, AES-256 at rest and TLS in transit; the certifications it lists are AWS's and Cognito's. No security.txt (404 on 1 October), no bug bounty (5).

Eraser API + MCP 57

Hosted MCP signs in with OAuth by default. The REST API takes one Bearer token per team, issued only to paid teams, with no scopes documented; deleting a token stops it at once, and organisation tokens act on every team in an organisation. Audit logs need a separate tenant-level key (22). OAuth-created files are private by default and files are archived rather than deleted, though diagrams and folders have delete endpoints, and there's no read-only token (8). Tools return team documents, diagrams and connected git and cloud data, and we found no prompt-injection guidance (3). An audit log API on Enterprise with ECS and Splunk CIM formats, plus a team usage endpoint (12). SOC 2 Type 2 and a penetration test report through the trust portal. No security.txt per the 30 September check, no bug bounty found (12).

Reliability Cloudviz API +5

Cloudviz API 20

No status page found; status.cloudviz.io didn't resolve on 1 October (0). No readable incident history (5). The API reference at cloudviz.io/developers is drawn by page script from an OpenAPI file that no served page links, so this run no longer reads it and its 1 October readings are struck. With it go the throttling description (rate, burst and a daily cap, no numbers) and the 429 and 202 definitions. No rate-limit numbers on any served page (0). Cloudviz's own sample client, linked from the docs, retries a 429 after half a second and a 202 after 10 seconds, the only retry guidance left, so the earlier partial 5 is kept as partly met (5). No SLA on any plan in the pricing page or the terms of 26 March 2019 (0). The API is sold as a working product, not a beta (10).

Eraser API + MCP 15

No status page found, and status.eraser.io doesn't resolve (0). No readable incident history (5). Rate limits aren't documented anywhere in the docs index (0). No 429 or retry guidance. The only documented brake is a team spend limit that blocks API calls at 100 per cent until the next month (0). No SLA on the pricing page (0). The API and hosted MCP are generally available (10).

Score by category

CategoryWeightCloudviz APIEraser API + MCPEdge
Reliability16%2015Cloudviz API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%837Eraser API + MCP +29
Agent ergonomics13%3534Cloudviz API +1
Security & auth14%3557Eraser API + MCP +22
Payments & pricing10%3053Eraser API + MCP +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%58Eraser API + MCP +3
Transparency & trust7%5050even
Negative events≤1500
TotalF 25.7/100F 36.2/100

Facts side by side

FactCloudviz APIEraser API + MCP
KindHTTP APIHTTP API
VendorCloudvizEraser
Hosted endpointhttps://api.cloudviz.iohttps://app.eraser.io/api
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
Tools exposednone42
Read-only variant documentedyesno
llms.txtnoyes
MCP registrynot listedio.eraser/eraser
Last releasenone2026-05-22
Terms last updated2019-03-26no date given
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Eraser API + MCP higher.

ReviewerCloudviz APIEraser API + MCP
GullBrowser and end-to-end tester 2/5 Two consoles before the first GET 3/5 Four dashboard switches before a token
QuillDocumentation and schema critic 3/5 Seven operations and a typed format enum 3/5 41 tools in the docs, 42 on the live server

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Cloudviz API

Cloudviz draws diagrams from the live AWS account through a read-only cross-account role with a per-customer external ID. AWS only, API access starts at the $49 a month Team plan, the API reference loads only in a browser, and there's no status page, changelog or dated update since March 2025.

Eraser API + MCP

Hosted MCP with OAuth and 42 tools, including manually_ tools that skip the AI when the agent writes the diagram code. No status page, rate limits, SLA or changelog, and the newest dated release found is the local server's March 2026 tag.

Before you call either

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 about 10 seconds and repeat the same GET until the diagram is ready, as the vendor's sample client does
  3. Pass a filter expression such as vpcId=vpc-123 or tag=stage:dev to keep the diagram small
  4. Ask the person to connect AWS with a read-only role before relying on the API

Eraser API + MCP

  1. Use manually_create_diagram with your own Eraser code when you know the structure. It skips the AI and its credits
  2. OAuth sessions spend the signed-in user's AI credits, API tokens spend the team's
  3. Call /render/elements ($0.20) when you already have diagram code; /render/prompt costs $0.80
  4. Set a spend limit before running in CI. At 100 per cent the API stops until the next calendar month

Questions

Which is better for AI agents, Cloudviz API or Eraser API + MCP?

Eraser API + MCP scores 36.2 (F) on agent readiness against Cloudviz API's 25.7 (F), and leads in 4 of 7 scored categories. Cloudviz API leads on reliability.

Do Cloudviz API and Eraser API + MCP need an API key?

Cloudviz API needs an API key. Eraser API + MCP takes an API key or an OAuth sign-in.

Can an agent call Cloudviz API and Eraser API + MCP without installing anything?

Yes. Cloudviz API has a hosted endpoint at https://api.cloudviz.io and Eraser API + MCP at https://app.eraser.io/api.

Other comparisons with Cloudviz API or Eraser API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.