Framer vs Canva

Agent ops

1. ai-native userAn agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them

   weight 2 · round to Canva
   Framer✓fullclaimed8/10

   Framer documents a write-capable external agent connection (Claude Code, Cursor, Codex) that can create/update/delete CMS items and modify canvas/components, backed by branching for safe review, plus a plugin surface and Server API for programmatic site automation. Missing for 10: independent/hands-on verification of the external-agent write capability and no public OpenAPI/formal API schema was found by the probe.

   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”

   proof ↗⚑ flag

   Canva✓fullprobed9/10

   Canva ships an official MCP server explicitly documented to let AI assistants create designs from text, edit existing designs via natural language, manage assets/brand kits, and export/resize outputs — a clear write-capable agent surface, corroborated by a dedicated MCP docs probe. This is backed further by the Connect APIs (write-capable REST API with OpenAPI/SDK generation) and Apps SDK for programmatic design manipulation. missing for 10: independent/hands-on third-party verification that the MCP write operations work reliably in practice.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

2. ai-native userAn agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface

   weight 2 · round to Canva
   Framer—none0/10

   Evidence covers AI agents editing designs, CMS, and publishing via a Server API and external-agent connections, but nothing documents a programmatic render/export surface for screenshots, images, or production-format exports (no export/render API endpoints, and probes for OpenAPI specs all 404).

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Canva✓fullprobed8/10

   Canva's Connect APIs and MCP server both provide documented programmatic export capability — the MCP server explicitly supports 'Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, etc.) and resize designs for different channels', and the Connect APIs allow creating/syncing designs and assets with OpenAPI-generated SDKs, confirmed via a live probe of the MCP docs. This directly satisfies an agent's need to render/export designs programmatically. Missing for 10: independent/hands-on confirmation of actual export calls succeeding (no third-party corroboration, only first-party docs), and the OpenAPI spec itself wasn't resolvable via direct probe.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

3. ai-native userMy coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design

   weight 3 · round to Framer
   Framer~partialclaimed7/10

   Framer explicitly markets a native 'External Agent' connection (explicitly positioned as replacing a separate MCP server) that gives coding agents like Claude Code, Cursor, and Codex direct access to canvas, components, CMS, and project context, including read/write CMS operations and branch-based change tracking. This closely matches the story's intent of pulling design context to implement changes, but the specific mention of 'screenshots' and 'variables' from the story isn't explicitly evidenced, and all evidence is first-party docs with no independent/hands-on corroboration of the external agent workflow. Missing for 10: explicit support for screenshots/variables extraction, independent developer confirmation of the external-agent integration working as described.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”

   proof ↗⚑ flag

   Canva~partialprobed6/10

   Canva has an official documented MCP server enabling AI assistants to search/retrieve designs, pages and folders, manage assets and brand kits, and export in multiple formats (PDF/PNG/JPG/etc.), which covers much of 'pulling real design context' for an agent to act on. However, the story's specific terms — frames, variables, component mappings — aren't explicitly evidenced, and there's no independent/hands-on confirmation that a coding agent can actually reconstruct implementation-level design context via this server. Missing for 10: explicit support for design variables, frame-level structural access, component-to-code mapping, and third-party corroboration of agent workflows.

   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design discovery:** Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Framer✓fullprobed8/10

   A direct probe confirms Framer serves a live llms.txt file (HTTP 200) with structured content describing the product and linking to migration/agent docs, and Framer's own docs explicitly reference this file's content, giving concrete first-party evidence an AI agent can be pointed at it. missing for 10: independent/third-party confirmation that agents successfully consume this llms.txt in practice, and broader agent-oriented doc coverage beyond this single file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.framer.com/llms.txt # Framer > Framer is an AI website builder for designers and teams. Generate ed…”
   • [claimed-docs] “Switch to Framer](https://www.framer.com/switch/?md): Migration from another builder.”
   • [claimed-docs] “Framer allows you to host static files directly on your site or custom domain. This feature is available on the **Pro**, **Enterprise**, and…”

   proof ↗⚑ flag

   Canva✓fullprobed8/10

   Canva confirms an accessible llms.txt file (HTTP 200) plus multiple scoped llms.txt files for sub-docs (e.g., scim/llms.txt, admin/llms.txt, audit-logs/llms.txt) and dedicated .md docs pages (mcp.md, connect.md, apps.md) explicitly structured for agent consumption. missing for 10: independent/third-party confirmation of an agent successfully using llms.txt to navigate docs, and a root-level single canonical llms.txt covering all products rather than fragmented per-section files.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.canva.dev/llms.txt # Canva Developers Documentation This file lists documentation for Canva product…”
   • [claimed-docs] “Use the SCIM API to automate the provisioning of Canva user accounts for your team.”
   • [claimed-docs] “The Canva Admin API lets you manage teams, groups, and users in a Canva organization.”
   • [claimed-docs] “Canva provides audit logs that contain records of user activities in Canva, such as installing a Canva App, exporting a design for download,…”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Canva
   Framer~partialprobed3/10

   Framer advertises a Server API to 'automate publishing' and integrate with external products/agents, which implies some programmatic/headless control, but there is no documented CLI, headless mode, or CI-specific workflow, and probes show no OpenAPI/API spec is publicly discoverable (404s). Missing for 10: concrete CI/headless setup docs, API reference/spec, and evidence of automated pipeline usage beyond marketing blurbs.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Canva~partialprobed5/10

   Canva's Connect APIs and bulk/personalization features (canva-docs-2, canva-docs-7, canva-docs-8, canva-docs-16, canva-docs-26) show that programmatic, non-interactive design generation and export are possible, and an OpenAPI description exists for SDK generation (canva-docs-31, canva-docs-36) which could support CI pipelines. However, Connect APIs are OAuth-based integrations meant for user-authorized platforms, not clearly documented as headless/service-account CI automation, and a probe for a hosted OpenAPI spec returned 404s (canva-probe-3), suggesting the automation surface is less mature for pure CI use. Missing for 10: explicit CI/service-account authentication flow, documented headless execution examples, and a verifiable OpenAPI spec endpoint.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Automatically create resized versions of designs in new dimensions, formats, or aspect ratios.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Framer—none0/10

   Framer explicitly states it does not use or require MCP: 'Framer doesn't require a separate MCP server... without manual MCP setup' (framer-docs-34). Its actual capability runs in the opposite direction — external agents like Claude Code/Cursor connect INTO Framer to use Framer's canvas/CMS as their tool, not Framer consuming external MCP servers' tools. No evidence exists of Framer acting as an MCP client that plugs in third-party MCP servers.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”

   proof ↗⚑ flag

   Canva—none0/10

   All evidence describes Canva exposing an official MCP *server* so external AI assistants (Claude, ChatGPT, etc.) can call Canva's own design tools (canva-docs-5, canva-docs-28, canva-probe-4) — the opposite direction of the story, which asks whether Canva itself can act as an MCP client plugging into external MCP servers to use their tools. No evidence shows Canva consuming or configuring external MCP servers.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “If you're a user wanting to connect your personal AI assistant to Canva's AI Connector, see our Help Center”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Canva
   Framer—none0/10

   Framer explicitly states it does not offer an MCP server, instead providing a proprietary 'External Agent connection' as an alternative to MCP (framer-docs-34). Since the story specifically asks for an official MCP server, and Framer's own docs assert this is unnecessary and unsupported by design, there is no evidence of an actual MCP server implementation.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”

   proof ↗⚑ flag

   Canva✓fullprobed9/10

   Canva ships an official MCP server (canva-docs-28, canva-probe-4) that lets AI assistants connect via natural language to Canva's design capabilities, with documented features spanning design generation, editing, discovery, export, asset/brand management, and collaboration (canva-docs-17 through 22, 33-35). Missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice.

   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Canva
   Framer—none0/10

   Evidence shows Framer offers a Server API, plugins, and 'External Agent' connections for tools like Claude Code/Cursor/Codex, but nowhere does it mention an official Framer CLI tool for AI-native workflows.

   ⚑ flag

   Canva~partialprobed5/10

   Canva does ship an official CLI, but it is scoped narrowly to creating and managing Canva Apps (the Apps SDK), not a general-purpose CLI for AI-native workflows like design generation, export, or automation via Connect APIs — those are exposed via APIs/MCP, not the CLI. missing for 10: evidence of CLI supporting broader AI-native tasks (design generation, bulk export, Connect API operations), independent/hands-on usage reports.

   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Canva
   Framer~partialprobed6/10

   Framer documents a Server API for automation/publishing and CMS API access, and explicitly supports external AI agents (Claude Code, Cursor, Codex) reading/writing CMS collections via a documented connection flow (framer-docs-5,17,30,39,40,18,24,34). However, probes could not locate any formal API reference/spec (openapi.json/swagger 404s) or detailed endpoint documentation, and there's no independent/community corroboration of developers actually using the Server API. Missing for 10: a discoverable formal API reference/spec, authentication/rate-limit details, and independent developer testimonials confirming API usability.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Canva✓fullprobed8/10

   Canva provides well-documented Connect APIs with an OpenAPI description for client SDK generation, plus Apps SDK, Admin API, SCIM API, and a first-party MCP server enabling AI assistants to drive Canva programmatically — directly matching an AI-native user's ability to drive the product via public API. Missing for 10: independent hands-on corroboration of API robustness/rate limits and a directly resolvable public OpenAPI file (probe found candidate OpenAPI endpoints 404, though docs claim one exists).

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Framer—none0/10

   Framer documents a Server API and an 'External Agent' connection that lets tools like Claude Code or Cursor read/write CMS data and canvas content, with branching as a safety net for undoing changes — but nothing describes issuing scoped, least-privilege, or permission-limited API credentials/tokens for agents. Missing for 10: any mention of API key scopes, granular permission levels, token expiration/rotation, or role-based credential issuance for agent access.

   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”

   proof ↗⚑ flag

   Canva—none0/10

   While Canva exposes Connect APIs, OAuth-based integrations, and an MCP server for AI assistants, none of the evidence describes issuing scoped or least-privilege credentials specifically for an agent (e.g., granular OAuth scopes, per-agent API keys, or restricted permission sets). Private integrations are gated by plan tier (docs-41) rather than granular scoping, and MCP/AI Connector docs discuss connecting an assistant but not credential scoping controls. Missing for 10: explicit scope/permission model for API keys or OAuth tokens issued to agents, documentation of least-privilege credential issuance, and any audit/control mechanism tied to agent-specific access.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “If you're a user wanting to connect your personal AI assistant to Canva's AI Connector, see our Help Center”
   • [claimed-docs] “Private integrations can only be used by your team on a Canva Enterprise plan.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Canva
   Framer~partialprobed6/10

   Framer documents a Server API, plugin SDK, code components/overrides, and an external agent connection for building integrations against official interfaces, but there's no discoverable OpenAPI spec (probe found 404s across candidate paths) and no independent/hands-on developer corroboration of building against these SDKs. missing for 10: publicly discoverable API reference/OpenAPI spec, independent developer corroboration, SDK versioning/language support details.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Canva✓fullprobed8/10

   Canva provides official SDKs (Apps SDK, Connect APIs) plus an OpenAPI description enabling generated client SDKs in various languages, a CLI for app development, and an official MCP server for AI-native integration—covering the core of building against official SDKs. Missing for 10: independent/hands-on developer corroboration beyond first-party docs, and the openapi.json probe returned 404 suggesting the spec isn't trivially discoverable at expected paths.

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Framer—none0/10

   Evidence covers Framer's Server API, external agent connections, and plugins, but there is no mention of webhooks or event subscription mechanisms anywhere in the docs or probes; OpenAPI probe also returned 404s with no webhook spec found.

   ⚑ flag

   Canva—none0/10

   No evidence of any webhook/event-subscription capability in the Canva Connect APIs, MCP server, or other docs — only REST-style APIs, SCIM, audit logs, and MCP tool interactions are described. missing for 10: any mention of webhooks, event subscriptions, or push notifications for state changes.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Framer
   Framer~partialclaimed4/10

   Framer's AI agent can restructure and suggest layout changes based on generic 'conversion best practices' (framer-docs-31/38) and manages/organizes CMS data (framer-docs-8/46), which is adjacent to data-driven suggestions, but there is no evidence of the agent analyzing a user's actual site/traffic data to surface analytical insights (e.g., performance, SEO, or visitor-behavior insights) — it is generative/design assistance rather than data-insight generation. Missing for 10: evidence of analytics-based insight generation, data pattern analysis, or dashboards summarizing user's own data trends.

   • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ”
   • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ, and make sure every s…”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Manage more. Publish faster. The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content …”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack shows Canva letting users import external data to drive design generation, bulk creation, and personalized template population (canva-docs-7, canva-docs-8, canva-docs-32), but nothing shows Canva's AI analyzing a user's own data to surface insights or proactive suggestions (e.g., analytics-style recommendations). This is closer to data-driven content generation than 'AI-generated insights and suggestions from my data,' so there is no concrete evidence the described capability exists.

   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Framer~partialclaimed4/10

   Framer offers a Server API to 'automate publishing' and lets external agents (Claude Code, Cursor, Codex) connect to read/write CMS and canvas content, which could be wired into autonomous workflows, but all documented agent interactions (framer-docs-6/7/26) are conversational/on-demand rather than scheduled or self-running background automations. There's no evidence of triggers, schedules, or persistent background jobs — only API/connection primitives a developer would need to build such automation themselves. missing for 10: evidence of scheduled/triggered background jobs, autonomous run history or logs, native workflow/automation builder distinct from on-demand AI agent editing.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”

   proof ↗⚑ flag

   Canva~partialclaimed4/10

   Canva provides integration surfaces (Connect APIs, Apps SDK, Bulk create, Brand Template autofill, MCP server) that let developers or AI assistants trigger Canva actions programmatically, but these are all invoked by an external caller rather than being a built-in autonomous scheduler or background automation engine within Canva itself. Missing for 10: evidence of native scheduled/triggered automations, event-driven workflows, or an 'autopilot' feature that runs without external initiation.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Framer
   Framer✓fullclaimed7/10

   Framer ships multiple built-in AI agents (design agent, CMS agent, AI website generator) that users can delegate tasks to directly inside the product via natural-language prompts (e.g. 'make responsive', 'switch to dark mode', CMS setup) as shown in framer-docs-6,7,8,26,42,43,44,45,46. Missing for 10: independent/hands-on user reports specifically validating the built-in AI assistant's reliability and quality (community evidence available only covers older, unrelated Framer features like animations).

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Manage more. Publish faster. The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content …”

   proof ↗⚑ flag

   Canva~partialclaimed3/10

   Evidence mentions a 'Canva AI' feature only in passing (pasting links to add context to designs) but provides no detail on delegating broader tasks to a built-in assistant; most AI-related evidence instead describes the MCP server that lets *external* AI assistants control Canva, not an assistant embedded within Canva's own UI. missing for 10: documentation of an in-app AI assistant's task scope, examples of users delegating multi-step design tasks to it, and independent/hands-on confirmation of its capabilities.

   • [claimed-docs] “Bring content into Canva AI by pasting links from other platforms to design with more context.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Framer✓fullclaimed8/10

   Framer's docs show extensive natural-language operation: the built-in AI agent creates pages/sections/copy from prompts, restyles sites ('switch to dark mode', 'use Fraunces/Inter'), reorganizes layouts, and makes sites responsive purely from described intent, plus a CMS agent and external-agent integration (Claude Code/Cursor/Codex) that reads/writes CMS and canvas content via natural language, with branch-based safety for changes. missing for 10: independent/hands-on third-party corroboration of the AI/CMS agent actually working as described (community evidence only covers older non-AI Framer features).

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”

   proof ↗⚑ flag

   Canva✓fullprobed8/10

   Canva ships an official MCP server explicitly designed so AI assistants can operate Canva via natural language — supporting design generation, editing, discovery, asset/brand management, export, and comments through NL commands, and this is corroborated by a probe confirming the documented endpoint. This directly satisfies the AI-native natural-language operation story, though it relies on third-party AI clients rather than a native in-product NL interface. Missing for 10: independent/hands-on user reports of NL command reliability, and evidence of a first-party conversational interface within Canva itself.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Framer—none0/10

   Framer documents a Server API, Plugins API, and Code Components, but nothing shows an interactive API reference with runnable/try-it examples; probe evidence explicitly found no OpenAPI/swagger spec (404s at all candidate paths), suggesting no such interactive reference exists.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Canva—none0/10

   Canva documents an OpenAPI description for its Connect APIs (used for generating client SDKs) but there is no evidence of an interactive API reference with runnable/try-it examples; probes for openapi.json/swagger endpoints returned 404s, suggesting no live interactive console is exposed.

   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Canva
   Framer—none0/10

   Framer offers a Server API and llms.txt, but the probe explicitly found no OpenAPI/swagger spec at any standard location, and no docs mention a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”

   proof ↗⚑ flag

   Canva✓fullprobed7/10

   Canva's developer docs explicitly state it provides an OpenAPI description of the Connect APIs that can be used with code-generation libraries to produce client SDKs, directly matching the story. Confidence is tempered because the probe couldn't locate the actual spec file at common guessed paths (only generic /openapi.json etc. were tried, not the real documented location), so independent verification of downloadability is thin. Missing for 10: a probed/verified working download URL for the OpenAPI file and independent (non-vendor) confirmation it's actually fetchable.

   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Framer
   Framer~partialclaimed6/10

   Framer offers staging environments on a framer.app domain and automatic branching so AI agent changes happen in isolation from the live/main project, which functions as a sandbox against production data (framer-docs-10, framer-docs-11, framer-docs-25, framer-docs-36). However, this is framed around publishing workflow rather than an explicit 'sandbox for AI testing' concept, and there's no independent/hands-on verification of how well this isolation holds up in practice. missing for 10: independent corroboration of branch/staging isolation, explicit documentation framing this as an AI-testing sandbox rather than a publishing safety net, and detail on whether CMS data changes by agents are also fully isolated from production before merge.

   • [claimed-docs] “Staging environments. Test changes securely on a framer.app domain before pushing live.”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Branches. Work on a copy of your project and keep the original clean.”

   proof ↗⚑ flag

   Canva—none0/10

   No evidence of a sandbox/test environment separate from production data; Canva's docs describe live APIs, MCP server, and Connect APIs but nothing about a sandbox mode, test accounts, or mock environment for safe experimentation.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Framer—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; probes for OpenAPI specs returned 404s and the Server/Fetch API docs mention no versioning or deprecation terms.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Canva—none0/10

   Evidence shows Canva has Connect APIs, an OpenAPI description, SDKs, and an MCP server, but there is no mention anywhere of API versioning scheme or a documented deprecation policy for these APIs; the OpenAPI spec itself isn't even discoverable at expected endpoints (canva-probe-3). missing for 10: explicit API versioning scheme, documented deprecation/sunset policy, changelog or migration guides for breaking changes.

   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

Ai

1. designerBuilt-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editor

   weight 1 · round to Framer
   Framer~partialclaimed3/10

   Framer's AI agent can generate pages, sections, copy, and visuals (framer-docs-6, framer-docs-26, framer-docs-42) and adjust layout/typography, which touches copy suggestions and some visual generation, but there is no evidence of dedicated asset-chore tools like image generation, background removal, or content-aware fill inside the editor. missing for 10: dedicated image generation tool, background removal feature, content-aware fill capability, hands-on/independent verification of these specific asset tools.

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack only covers developer-facing surfaces (Apps SDK, Connect APIs, MCP server, Admin/SCIM/audit APIs) and never mentions Canva's native in-editor AI asset tools like Magic Media image generation, Magic Eraser/background removal, Magic Edit content-aware fill, or Magic Write copy suggestions used directly by a designer inside the editor. Missing for 10: any documentation of built-in Magic Studio-style tools (image generation, background removal, content-aware fill, copy suggestions) operating natively within the Canva editor UI.

   ⚑ flag

2. designerGenerate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually produces

   weight 2 · round to Framer
   Framer✓fullclaimed8/10

   Framer's docs describe a native AI agent that generates editable pages, sections, copy, and visuals from prompts, with examples of full mockup edits (typography, grid layouts, brand colors, dark mode, responsive breakpoints, image-based starting points), and lets designers keep refining in canvas after generation. This directly matches the story of prompt-driven first drafts/layouts/mockups, though evidence is entirely vendor-sourced with no independent hands-on verification of AI-generation quality — missing for 10: independent/hands-on confirmation that generated designs are production-quality, and any documented limitations of the AI design agent.

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”

   proof ↗⚑ flag

   Canva~partialprobed6/10

   Canva's docs describe design generation and editing from natural language via its MCP server (canva-docs-17, canva-docs-18, canva-docs-28, canva-docs-33), which lets AI assistants create and modify designs from text descriptions and specifications, plus discovery, export, and asset management. However, this capability is delivered through an external MCP integration/AI connector rather than a native in-editor 'Magic Design'-style prompt feature, and there's no independent/hands-on evidence confirming quality of generated mockups. Missing for 10: first-party in-product documentation of native prompt-to-design (e.g., Magic Design) generation, independent hands-on verification of output quality, and confirmation this works without third-party AI tool setup.

   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design generation:** Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design discovery:** Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Canva
   Framer~partialclaimed6/10

   Framer docs show AI-agent driven bulk operations such as site-wide typography/color/theme changes across all pages (framer-docs-19,27,37), CSV bulk import of CMS collections with row-level linking (framer-docs-9,21), and external agents able to create/update/delete many CMS items via API (framer-docs-18,24,35). This supports bulk operations across many items in CMS/design contexts, but there's no documentation of scale limits, batch API endpoints, or performance at large volumes. Missing for 10: explicit bulk/batch API documentation with scale guarantees, independent verification of bulk operations succeeding at scale, and rate-limit/performance details.

   • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”

   proof ↗⚑ flag

   Canva✓fullclaimed7/10

   Canva explicitly supports bulk operations via Bulk Create with data import, personalized Brand Template population at scale, and Connect APIs to sync/create many designs/assets programmatically, plus MCP/API access for AI-native automation across many items. Missing for 10: independent/hands-on verification of scale limits, no explicit rate-limit or batch-size documentation, and no third-party confirmation of true 'many items' throughput.

   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Framer—none0/10

   Evidence shows Framer's API, plugins, and AI agents that can be manually invoked to modify a site, and an API to 'automate publishing,' but nothing describes a rule engine or event-trigger system where a user defines 'when X happens, do Y' automation. missing for 10: any event-trigger/rule definition mechanism, conditional logic, or workflow automation builder within Framer.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”

   proof ↗⚑ flag

   Canva—none0/10

   Canva's evidence covers APIs, apps, MCP server, bulk creation, and integrations, but nothing describes user-defined rule/trigger automation (event-condition-action logic) that fires actions automatically on events. No workflow/automation-rule engine, webhooks-as-triggers, or 'when X happens do Y' capability is documented.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Framer—none0/10

   Framer's evidence covers AI agents editing sites, CMS, publishing, plugins, and APIs, but there is no mention of scheduling recurring jobs, cron-like automation, or workflow triggers of any kind. Automate publishing via API is a manual/programmatic action, not a recurring scheduled job.

   ⚑ flag

   Canva—none0/10

   The evidence covers Canva's Connect APIs, Apps SDK, MCP server, and bulk creation features, but none of it describes any scheduler, cron-like trigger, or recurring/automated job execution capability. Bulk create and template population are one-shot batch operations, not recurring scheduled workflows.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Framer
   Framer✓fullclaimed8/10

   Framer documents automatic version history with instant rollback, plus branching that isolates every external-agent change so it can be reviewed, undone, or merged — directly matching version/review/rollback for automations run by AI agents. Missing for 10: independent/hands-on confirmation of rollback and branch-merge workflows in practice, and detail on granular diff/review UI beyond marketing docs.

   • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “Staging environments. Test changes securely on a framer.app domain before pushing live.”

   proof ↗⚑ flag

   Canva—none0/10

   Evidence shows audit logs tracking user activity, but no documentation of versioning, review, or rollback specifically for automations (Connect API integrations, MCP workflows, or bulk create jobs). There's no mention of automation history, diffing, approval workflows, or reverting automated changes.

   • [claimed-docs] “Use audit logs to track changes made by your team in Canva.”
   • [claimed-docs] “Canva provides audit logs that contain records of user activities in Canva, such as installing a Canva App, exporting a design for download,…”

   proof ↗⚑ flag

Collaboration

1. product managerComment directly on designs, mention teammates, and resolve threads so review happens in the file, not in email

   weight 2 · round to Canva
   Framer—none0/10

   Evidence covers branching, version history, AI agents, CMS, and plugins, but nothing about in-file commenting, @mentions of teammates, or resolving comment threads for design review. Missing for 10: any mention of a commenting feature, mention/notification system, or thread resolution workflow.

   ⚑ flag

   Canva~partialclaimed5/10

   Evidence confirms Canva supports commenting on designs and even integrating comments into external workflows (canva-docs-9, canva-docs-22, canva-docs-37), implying in-file review is possible, but there is no direct documentation of @mentioning teammates or explicitly 'resolving' comment threads within the editor. missing for 10: explicit documentation of @mention functionality, thread resolution/closing feature, and any first-party or independent confirmation of the full in-app review workflow.

   • [claimed-docs] “Receive and reply to Canva comments from any platform and simplify team communication.”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”

   proof ↗⚑ flag

2. designerMy whole team can edit the same file simultaneously with live cursors and instant sync

   weight 3 · round drawn
   Framer—none0/10

   The evidence pack includes docs on branching, version history, and staging (framer-docs-11, framer-docs-47) but contains no mention of real-time multiplayer editing, live cursors, or instant sync between simultaneous editors — the actual claim in the story. Missing for 10: any documentation of live cursors, simultaneous multi-user canvas editing, or real-time presence indicators.

   ⚑ flag

   Canva—none0/10

   The evidence pack focuses entirely on developer APIs, SDKs, MCP servers, and admin/provisioning tools; there is no mention of real-time multi-user editing, live cursors, or simultaneous in-editor collaboration features that are core to this story.

   ⚑ flag

Design systems

1. designerManage design tokens or variables — colors, spacing, typography — with modes or themes applied across designs

   weight 2 · round drawn
   Framer—none0/10

   Evidence shows Framer's AI agent can restyle colors/typography/light-dark mode on request (framer-docs-27, framer-docs-37, framer-docs-19), but there is no documentation of an actual design-token or variables system with reusable modes/themes applied consistently across designs, akin to Figma variables. Missing for 10: token/variable definition, mode-based theme switching infrastructure, cross-file/theme propagation evidence.

   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”

   proof ↗⚑ flag

   Canva—none0/10

   Canva's evidence covers Brand Templates, Apps SDK, Connect APIs, and MCP integrations, but nothing describes design tokens/variables (colors, spacing, typography) as reusable, mode-based theme objects applied programmatically across designs — Canva's brand kit concept is not documented as a token/variable system with theme modes.

   ⚑ flag

2. designerBuild reusable components with variants and per-instance overrides that stay linked to their source

   weight 3 · round to Framer
   Framer~partialclaimed3/10

   Evidence only touches tangentially on component reuse — Code Components with visual controls and Code Overrides (HOCs to modify Layer/Component properties) hint at reusable, overridable components, but nothing explicitly describes variants or per-instance overrides that stay linked to a master component/source as in a design-system workflow. Missing for 10: explicit documentation of component 'variants', proof that per-instance overrides remain linked/syncable to the source component, and any hands-on/community confirmation of this specific workflow.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack covers Canva's APIs, SDKs, MCP server, and Brand Templates but contains no mention of a component system with variants, per-instance overrides, or linked source instances (like Figma-style components). Brand Templates allow personalization but are not described as variant-based linked components. Missing for 10: any documentation of a component/variant system, linked instance overrides, or source-of-truth syncing mechanism for design elements.

   ⚑ flag

3. designerShared libraries publish components and styles across files and projects, with controlled updates when the source changes

   weight 2 · round to Canva
   Framer—none0/10

   Framer's evidence covers code components, plugins, branching, and CMS collections within a single project, but there is no documentation of a shared/team library mechanism that publishes components or styles across separate files or projects with controlled update propagation (the Figma-style library model). Missing for 10: any mention of a cross-project component/style library, library publishing workflow, or update-notification/accept-update mechanism.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”

   proof ↗⚑ flag

   Canva~partialclaimed4/10

   Canva offers Brand Kits and Brand Templates that centralize on-brand assets/styles for teams to reuse across designs (canva-docs-15, canva-docs-7, canva-docs-20), which is the closest analog to a shared component library. However, there is no evidence of a true library-linking mechanism where edits to a source style/component automatically or optionally propagate updates to files that already used it, which is the core of the story. missing for 10: documentation of update propagation/versioning when a Brand Template or Brand Kit element changes, evidence of per-instance 'update available' notifications, independent confirmation of this workflow in practice.

   • [claimed-docs] “Make Brand Templates easily accessible, so teams can quickly create and edit on-brand designs.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”

   proof ↗⚑ flag

Handoff

1. developerDesigns map to production code — component-to-code mappings or direct design-to-code output I can actually ship

   weight 2 · round to Framer
   Framer~partialcommunity7/10

   Framer supports genuine dev-facing code integration: Code Components (custom React components with visual controls), Code Overrides (HOCs), a Server API, and native external-agent access letting Claude Code/Cursor/Codex read/write the live project and CMS with branch-based review before merge. Community evidence corroborates that Framer's React-based model lets designers hand off working code to developers. However this is not a classic 'export design to code' pipeline (no Figma-style code export or OpenAPI-documented flow was found), and independent verification is thin/dated. missing for 10: independent hands-on proof of shipping exported production code, more recent community validation of the external-agent/dev handoff workflow.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”

   proof ↗⚑ flag

   Canva—none0/10

   Canva's developer docs cover Apps SDK, Connect APIs, MCP server, and CLI for building integrations, but none of the evidence describes design-to-code output or component-to-code mappings that map a Canva design to shippable UI code (e.g., React/CSS export) as design tools like Figma do.

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

2. developerInspect any layer and get measurements, styles, assets, and code snippets (CSS/iOS/Android) without an editor seat

   weight 3 · round drawn
   Framer—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Framer
   Framer~partialprobed6/10

   Framer exposes a Server API, external-agent connections (Claude Code/Cursor/Codex) with read/write CMS access, branching for review, and a plugin system that covers many editor actions (framer-docs-5,17,18,24,34,35,36) — a real, substantive API surface for automation. But there's no evidence of full UI/API parity: no OpenAPI/spec discoverable (framer-probe-3 shows 404s across candidate spec paths), and the docs describe specific supported actions (CMS CRUD, canvas edits via agent, publishing) rather than a claim that literally everything achievable in the UI (e.g. fine-grained styling, animation editing, plugin marketplace management) is scriptable via API. Missing for 10: a documented comprehensive API/OpenAPI reference proving parity, explicit vendor claim of 'anything in UI = anything via API', and independent/hands-on verification of that parity.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Canva~partialclaimed5/10

   Canva offers substantial API surface (Connect APIs, Apps SDK, SCIM, Admin API, MCP server) covering design creation, editing, export, comments, and asset management, but this is a curated set of endpoints rather than full parity with the UI editor's rich manual design capabilities (e.g. free-form drag-and-drop editing, most granular design tools). No evidence confirms full UI-API parity; the docs describe specific supported operations, not a claim of complete equivalence. Missing for 10: explicit parity claim or evidence that every UI editing action (e.g. fine-grained manual layout, all effects/filters) is API-accessible, and independent verification of coverage limits.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Canva
   Framer—none0/10

   Evidence shows Framer offers a Server API, CMS API, and CSV import for content, but nothing indicates the ability to export a full site (design, code, CMS data) into open, portable formats for migration away from Framer; only 'migrate to Framer' flows are documented, not exit/export paths.

   • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
   • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”

   proof ↗⚑ flag

   Canva~partialclaimed4/10

   Canva supports exporting individual designs in open, standard formats (PDF, PNG, JPG, PPTX, MP4) via both the Connect API and the MCP server, giving users a way to pull their design content out in interoperable formats. However there is no evidence of a comprehensive account-level data export (brand kits, comments, team assets, settings, history) or a documented 'export all my data' / account deletion-and-portability feature that would let an AI-native user fully leave with everything intact. missing for 10: bulk/account-wide data export, documented data portability or GDPR-style export tool, evidence of exporting non-design data (comments, brand assets, admin/audit data) in open formats.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Framer—none0/10

   Framer is closed-source proprietary SaaS; no evidence pack item mentions an open-license source availability, and this is a mainstream commercial product with no indication of open-sourcing its codebase.

   ⚑ flag

   Canva—none0/10

   Canva is closed-source SaaS; the evidence pack only covers APIs, SDKs, MCP server, and developer docs — none of it indicates any open-license availability of Canva's own product source code.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Framer—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Plugins

1. developerA documented plugin API with typings and samples lets me build and distribute my own editor extensions

   weight 2 · round to Canva
   Framer~partialclaimed6/10

   Framer documents a Plugins API for building editor extensions (small apps that interact with the Editor/CMS, insert layers/images/code components) with a dedicated developer docs section, plus adjacent APIs like Code Components and Server API. However, the evidence pack doesn't show explicit TypeScript typings references or concrete code samples/SDK repo, and there's no distribution/marketplace mechanism described. missing for 10: explicit typings documentation, concrete code samples/starter templates, and a distribution/marketplace mechanism for sharing plugins.

   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”

   proof ↗⚑ flag

   Canva✓fullprobed8/10

   Canva provides a documented Apps SDK for building editor extensions, a CLI for creating/managing apps, and distribution via public Apps Marketplace or private team sharing, matching the developer story closely. missing for 10: independent/hands-on corroboration of typings quality and sample completeness, and a working OpenAPI/typings endpoint (probe found openapi.json paths returning 404).

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [claimed-docs] “You can then either distribute the app publicly via the Apps Marketplace, or share it privately with members of your team.”
   • [claimed-docs] “Team apps are created solely for a team using Canva, such as an app created to integrate into a specific system.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

2. designerExtend the editor from a large plugin community or marketplace — icons, data fillers, accessibility checkers, and more

   weight 2 · round to Canva
   Framer~partialclaimed5/10

   Framer's docs confirm a plugin system where developers build 'small apps' that can interact with the editor and CMS (inserting images, layers, code components, modifying canvas), which is the technical foundation for a plugin ecosystem. However, the evidence never mentions a marketplace, community size, or specific plugin categories like icon packs, data fillers, or accessibility checkers as the story asks. Missing for 10: evidence of an actual marketplace/directory, plugin discovery UX, and named example plugins matching icons/data/accessibility use cases.

   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”

   proof ↗⚑ flag

   Canva~partialprobed6/10

   Canva has a real extensibility ecosystem: the Apps SDK/CLI for building apps, an Apps Marketplace for public distribution, and team-private app sharing — directly supporting icon/data/accessibility-style plugins built by third parties. However, evidence is entirely first-party docs describing the SDK/marketplace mechanics; there's no independent evidence of marketplace size, breadth of existing third-party plugins (icons, accessibility checkers, data fillers), or community adoption. Missing for 10: independent verification of marketplace scale/quality, concrete examples of third-party apps in categories named in the story, user reviews or hands-on discovery of the marketplace.

   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [claimed-docs] “You can then either distribute the app publicly via the Apps Marketplace, or share it privately with members of your team.”
   • [claimed-docs] “Make apps for your team and choose who can use them.”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “Team apps are created solely for a team using Canva, such as an app created to integrate into a specific system.”
   • [claimed-docs] “Learn how you can turn your app into a business.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

Pricing

1. product managerPublished plan pricing makes seat types, tiers, and AI-feature gating clear before procurement

   weight 1 · round drawn
   Framer—none0/10

   The evidence pack contains no pricing page, plan tiers, seat types, or AI-feature gating details — only one mention that a static-file hosting feature is limited to Pro/Enterprise plans, which does not constitute published plan/seat/AI-gating clarity. No pricing comparison table or plan documentation is present anywhere in the pack.

   ⚑ flag

   Canva—none0/10

   The evidence pack is entirely developer/API documentation (Connect APIs, Apps SDK, MCP, SCIM, Admin API) and contains no pricing page, plan comparison, seat-type breakdown, or AI-feature gating disclosure that a procurement-focused product manager would need. Only one mention ('Private integrations can only be used by your team on a Canva Enterprise plan') hints at plan gating but is far from a published pricing/tier matrix.

   • [claimed-docs] “Private integrations can only be used by your team on a Canva Enterprise plan.”

   proof ↗⚑ flag

2. designerThe free tier supports real design work — usable editor and collaboration without a paid seat

   weight 2 · round drawn
   Framer—none0/10

   The evidence pack contains no mention of Framer's free tier, its editor limitations, or free-tier collaboration features; all docs focus on AI agents, CMS, publishing, and plugins. No pricing or free-plan details are cited anywhere in the pack, so there is no basis to confirm the free tier supports real design work or collaboration.

   ⚑ flag

   Canva—none0/10

   The evidence pack is entirely developer/API-focused (Connect APIs, Apps SDK, MCP server, SCIM, audit logs, admin API) and contains nothing about the consumer free-tier editor, its feature set, or free collaboration capabilities; one entry even implies enterprise-only integrations. No evidence supports or refutes what the free tier includes for a designer doing real design work.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Framer—none0/10

   No evidence in the pack addresses data residency, region selection, or data storage location controls for Framer; all evidence concerns AI agents, CMS, plugins, and publishing features unrelated to data residency.

   ⚑ flag

   Canva—none0/10

   No evidence in the pack mentions data residency, regional storage options, or location controls for Canva data; documentation covers APIs, SDKs, audit logs, and provisioning but not data residency/region choice.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Framer—none0/10

   No evidence in the pack addresses data usage for AI training, opt-out controls, or any privacy policy statement regarding training data; all evidence concerns AI agent features, plugins, and site publishing.

   ⚑ flag

   Canva—none0/10

   The evidence pack contains only Canva developer docs about APIs, SDKs, MCP servers, and admin/audit tools — nothing addresses AI training data usage policies or opt-out controls for user content. Missing for 10: any documentation on AI training data policy, opt-out settings, or privacy controls related to model training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Framer—none0/10

   The evidence pack covers Framer's AI agent, plugins, API, CMS, and version control/branching features, but contains no mention of data retention policies, data deletion controls, or privacy/compliance settings for AI-native workflows. Missing for 10: any documentation on data retention periods, user-initiated data deletion, or privacy controls specific to AI agent interactions.

   ⚑ flag

   Canva—none0/10

   Evidence covers audit logs, SCIM provisioning, and admin/team management APIs, but nothing addresses data retention policies or user-initiated data deletion controls for AI-native usage (e.g., MCP/AI connector data handling, deletion of AI-processed content, retention settings).

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Framer—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Framer's AI features or platform; all documentation covers unrelated capabilities (agents, CMS, plugins, publishing).

   ⚑ flag

   Canva—none0/10

   No evidence pack item addresses telemetry/usage-tracking opt-out settings for AI-native users; documentation covers APIs, SDKs, MCP server, audit logs, and provisioning but nothing about disabling telemetry collection.

   ⚑ flag

1. designerPrototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product

   weight 1 · round to Framer
   Framer!disputedcontradicted6/10

   Framer's docs and community evidence confirm rich prototyping behavior — animated menus, carousels, code overrides, data-driven components (docs-45, docs-32, comm-4, comm-5) — but hands-on reports document concrete failures that undercut the 'feels like the real product' promise: animations distort during size/geometry changes, performance is inconsistent (60fps then chugging) on the same device, and users found Framer 'falls through' vs alternatives like react-spring when chaining multiple interactive animated nodes (comm-6, comm-7, comm-9). Missing for 10: independent verification that these animation glitches are resolved, and evidence of robust variable/conditional-logic support beyond CMS data binding.

   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Fetch Building API endpoints that designers can use on their Framer sites without code.”
   • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”
   • [community] “As a ux designer... this is quite an interesting tool if you design software. It gives a nice blend between design and code. Your prototypes…”
   • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
   • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
   • [community] “I feel react-spring is better suited for the job... tried them both with r3f, i think it's just about API design and framer starts to fall t…”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and automation/integration features, but contains no mention of interactive prototyping capabilities such as animated state transitions, conditional logic, variables, or scroll-triggered effects within Canva designs. This is a fair axis for a design tool to be judged on, but nothing in the pack shows Canva delivers it.

   ⚑ flag

2. designerWire screens into clickable prototypes with triggers, transitions, and overlays — no code required

   weight 2 · round to Framer
   Framer~partialcommunity4/10

   Evidence shows Framer supports animations/transitions (community: 'great for more advanced prototyping needs w/ animations/transitions', 'declarative approach to creating nice animations') and AI-driven interactive elements like 'sticky navbars, animated menus, interactive carousels' handled via prompts, but there is no explicit documentation of screen-to-screen click triggers or overlay linking (the core Figma-style prototyping flow), and community reports flag animation performance/rendering glitches that undercut confidence. missing for 10: explicit docs on multi-screen click triggers, overlay/modal linking, and independent confirmation of a smooth no-code prototyping flow.

   • [community] “Framer is great for more advanced prototyping needs w/ animations/transitions/etc, but Adobe XD is pretty good and fast for many needs, and …”
   • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
   • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”

   proof ↗⚑ flag

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Canvas

1. designerFrames can behave responsively — auto layout, constraints, and grids resize designs the way real UIs flex

   weight 2 · round to Framer
   Framer~partialclaimed6/10

   Framer's docs describe breakpoint-based responsive adaptation ('adapts your layouts across breakpoints, adjusting stacks, type sizes, spacing, and image crops') and general layout refinement (breakpoints, spacing) via its AI agent and canvas, which implies auto-layout/stack-style responsive behavior. However, there's no explicit documentation of manual constraints or grid systems, and no independent/hands-on corroboration of responsive resizing quality. missing for 10: explicit docs on constraints/grid systems, independent verification of resize fidelity across breakpoints, non-AI-agent manual workflow evidence.

   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack covers Canva's APIs, SDKs, MCP server, and admin/integration tooling, but contains no mention of responsive frames, auto layout, constraints, or grid-based resizing behavior akin to real UI flex layouts within the design editor itself. Design resizing mentioned (canva-docs-6, canva-docs-16) refers to static output resizing to new fixed dimensions, not dynamic responsive layout behavior.

   ⚑ flag

2. designerI get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design work

   weight 3 · round drawn
   Framer—none0/10

   The evidence pack is entirely about Framer's AI agents, CMS, publishing, plugins, and developer API — nothing addresses classic vector tools like pen/path editing, boolean operations, or precise alignment guides. No documentation or community evidence confirms these professional vector-editing capabilities.

   ⚑ flag

   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and automation/integration features, but contains no mention of pen/path tools, boolean operations, or precision alignment controls for vector editing. Canva is a template-driven design tool, so this axis is fair to ask, but nothing in the evidence supports professional vector-editing capability.

   ⚑ flag

Files

1. designerExport production assets — PNG, SVG, PDF, and more — with per-layer presets, scales, and slices

   weight 2 · round to Canva
   Framer—none0/10

   Framer is a website-builder/publishing tool, not a design/prototyping tool with layer-based asset export; the evidence pack contains no mention of PNG/SVG/PDF export, per-layer presets, scales, or slices — these are Figma/Sketch-style export features absent from Framer's docs.

   ⚑ flag

   Canva~partialclaimed4/10

   Canva's docs confirm multi-format export (PDF, PNG, JPG, PPTX, MP4) and automatic resizing to new dimensions/aspect ratios, covering the basic 'PNG, SVG, PDF, and more' export need, but there is no evidence of SVG export, per-layer export presets, or slice-based export controls akin to design-tool layer/slice workflows. missing for 10: SVG export support, per-layer export presets, and slice/scale export tooling.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Automatically create resized versions of designs in new dimensions, formats, or aspect ratios.”
   • [claimed-docs] “Canva Pro and above: Design resizing to new dimensions”

   proof ↗⚑ flag

2. developerThe file format is open or documented, so my designs stay portable and toolable outside the vendor's editor

   weight 1 · round drawn
   Framer—none0/10

   The evidence pack covers Framer's APIs, plugins, CMS, and AI agent integrations, but contains no mention of an open or documented native file format that would let designs be opened, edited, or version-controlled by external tools outside Framer's own editor/publishing pipeline. Version history, branching, and staging are all Framer-hosted features, not a portable file format.

   ⚑ flag

   Canva—none0/10

   Evidence shows only APIs (Connect API, Apps SDK, MCP) and export formats (PDF/PNG/PPTX/etc.) for integration, but no documented open native design file format — Canva's underlying .canva design representation itself remains proprietary and undocumented; users must go through the vendor's own APIs/exports to get data out, not a portable open format usable in other tools without Canva's platform.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

3. developerSelf-host the full design platform on my own infrastructure under an open-source license

   weight 2 · round drawn
   Framer—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. designerFull version history lets me name milestones, compare, and restore any earlier state of a file

   weight 2 · round to Framer
   Framer~partialclaimed5/10

   Framer's docs confirm automatic version history with one-click restore of any prior version (framer-docs-12, framer-docs-22) and branching to isolate changes (framer-docs-11, framer-docs-47), but there is no evidence of naming/labeling milestones or a side-by-side compare view between versions. Missing for 10: named milestone/checkpoint labeling, version comparison/diff view, independent hands-on confirmation of restore workflow.

   • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “Branches. Work on a copy of your project and keep the original clean.”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and admin/audit features, but contains no mention of file version history, naming milestones, comparing versions, or restoring earlier states of a design.

   ⚑ flag