Canva vs Rive

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
   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

   Rive✓fullprobed8/10

   Rive documents an MCP integration letting AI tools create/modify complex View Models, State Machines, Layouts, and Shapes directly in the Editor, plus RML (a text-based file format) explicitly designed so coding agents can build/modify Rive files programmatically, and a CLI for agent-driven generation. This goes beyond read-only access into genuine write-capable agent tooling. Missing for 10: independent/hands-on verification of the MCP tools working in practice and more detail on the write-scope limits of the MCP server.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/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
   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

   Rive!disputedcontradicted4/10

   Rive's runtimes expose a documented programmatic Renderer interface (rive-gh-1/2/3) and RML lets code/agents construct .riv content (rive-docs-13/20/25), and export docs describe exporting to 'websites, mobile apps, games, videos' (rive-docs-7/8) — suggesting a programmatic render/export surface. However, hands-on community feedback directly contradicts image/video export capability: users report 'no way to export movie files' and ask 'can I export video assets with this!?' with no answer (rive-comm-3, rive-comm-10), indicating the actual exportable surface is limited to the .riv runtime format rather than screenshots/images/production video as the story requires. Missing for 10: documented API/CLI for agent-triggered screenshot or image/video export, and confirmation this gap has been resolved.

   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   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 Canva
   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

   Rive~partialprobed5/10

   Rive documents an official MCP server connecting the Editor to AI tools, letting agents create/modify View Models (variable-like data), State Machines, Layouts, and Components (rive-docs-19, rive-docs-27, rive-docs-10, rive-docs-11). This covers some 'design context' elements (component mappings, variables via view models) but is framed as agents building/editing Rive content rather than pulling existing frames or screenshots for implementation elsewhere. Missing for 10: explicit screenshot/frame extraction capability, evidence of pulling existing design context (vs. generating new), and independent/hands-on confirmation of the MCP workflow.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Canva
   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

   Rive✓fullprobed7/10

   Rive's docs are served in agent-friendly markdown (docs/*.md return 200) and explicitly point agents to a documentation index at https://rive.app/docs/llms.txt for full-site context, satisfying the 'point an agent at llms.txt or agent-oriented docs' story even though the conventional root-level /llms.txt path 404s. Missing for 10: direct confirmation that /docs/llms.txt itself loads and contains a complete index, and no independent (non-vendor) corroboration of an agent successfully using it.

   • [probe] “PROBE llms.txt: HTTP 404 at https://rive.app/llms.txt”
   • [probe] “PROBE docs-md: HTTP 200 at https://rive.app/docs/getting-started/introduction.md > ## Documentation Index > Fetch the complete documentation…”
   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   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

   Rive~partialclaimed4/10

   Rive exposes open-source runtimes as libraries (rive-gh-1, rive-docs-21) and mentions a CLI for agent-driven generation and RML for text-based/coding-agent workflows (rive-docs-26, rive-docs-25, rive-docs-30), suggesting some scriptable/automatable path outside the interactive editor. However, there is no explicit documentation of headless rendering, CI pipeline integration, or automated test/build usage of the CLI or runtimes. Missing for 10: explicit headless/CI usage docs, CLI reference/flags, examples of automated pipeline integration, independent confirmation of non-interactive operation.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive✓fullprobed7/10

   Rive documents a first-party MCP integration letting users connect the Rive Editor to AI tools via MCP so AI can perform tasks like creating View Models, State Machines, Layouts, and Shapes, confirmed by both docs and a dedicated probe. Missing for 10: independent/hands-on verification of the MCP integration working in practice and details on which MCP clients/servers are supported beyond the editor's own tools.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

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

   weight 3 · round to Canva
   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

   Rive✓fullprobed8/10

   Rive's docs explicitly describe an official MCP server that connects the Rive Editor to AI agents/tools, letting AI handle View Models, State Machines, Layouts, Shapes, etc., and this is confirmed via a dedicated docs page and probe. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice beyond first-party docs.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Canva
   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

   Rive~partialclaimed3/10

   The Rive homepage claims users can 'let an agent generate them with the CLI' (rive-docs-26), indicating an official CLI exists for AI-agent workflows, but no other evidence pack item documents CLI installation, commands, or usage — most AI-agent tooling evidence instead centers on the MCP server and in-editor AI agent, not a standalone CLI. Missing for 10: dedicated CLI docs/reference, install instructions, command examples, and independent/hands-on corroboration of the CLI working.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Rive✓fullprobed8/10

   Rive documents open-source runtime APIs (web, mobile, game engines) for loading and controlling animations programmatically (rive-docs-21, rive-gh-1, rive-docs-14/15), plus a text-based file format (RML) explicitly designed for coding agents and automated workflows (rive-docs-13, 20, 25, 30), and an official MCP server/AI agent integration for driving the Editor via AI tools (rive-docs-19, 27, rive-probe-4, rive-docs-9/18). Together these give an AI-native user multiple documented, agent-friendly ways to control the product beyond the GUI. Missing for 10: a formal REST/OpenAPI-style public API (probe shows 404s for openapi/swagger endpoints) and independent third-party corroboration of programmatic API usage.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   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

   Rive✓fullclaimed8/10

   Rive documents open-source official runtimes (SDKs) for web, mobile, game engines, and other platforms, with a public GitHub repo (rive-runtime) implementing the loading/rendering API, plus explicit guidance on caching and using the same exported .riv file across supported runtimes. This directly satisfies 'build against official SDKs' for developers, including AI-native workflows via RML/MCP integration for programmatic file creation. Missing for 10: independent third-party corroboration of SDK quality/completeness across all listed platforms and more granular per-language SDK documentation (e.g., npm/Swift/Kotlin package specifics).

   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   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

   Rive—none0/10

   No evidence anywhere in the pack mentions webhooks, event subscriptions, or any push-notification API for Rive; the product is documented as a design/animation tool with editor, runtime, and MCP/AI-agent integrations, none of which reference webhook-based event delivery.

   ⚑ flag

Agentic features

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

   weight 2 · round to Canva
   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

   Rive—none0/10

   Rive's docs describe an AI agent, MCP integration, and CLI that generate animations/code when invoked by a user, but there is no evidence of scheduled, unattended, or continuously running background automations — all AI features described are user-triggered, session-based interactions within the Editor.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive✓fullclaimed8/10

   Rive documents a built-in AI agent inside the Editor that writes code, generates layouts, data models, view models, state machines, and animation, letting users delegate repetitive/complex tasks to it directly within the product. This is first-party documented with specific task examples, though there's no independent/hands-on corroboration of its real-world effectiveness. Missing for 10: independent verification of the AI agent's actual capability/reliability, more detail on scope/limits of delegation.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   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

   Rive~partialprobed6/10

   Rive documents a built-in AI agent and MCP integration that let users describe tasks in natural language to generate ViewModels, state machines, layouts, and animation code, plus a CLI for agent-driven generation (rive-docs-9,10,18,19,26,27). However, this is entirely first-party documentation with no independent or hands-on confirmation that natural-language commands reliably drive the full editor experience, and community feedback focuses on pricing/licensing rather than the AI agent's real-world behavior. Missing for 10: independent/hands-on verification of the AI agent's natural-language command success, broader coverage beyond docs-based claims, and detail on command scope/limits.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   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

   Rive—none0/10

   While Rive has extensive documentation (runtime parameters, data binding, RML), there is no evidence of an interactive API reference with runnable/live code examples, and the OpenAPI probe returned 404s with no playground or sandbox mentioned.

   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   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

   Rive—none0/10

   A direct probe for OpenAPI/swagger spec endpoints (openapi.json, swagger.json, etc.) returned 404 for all candidates, and no docs mention a machine-readable API spec being downloadable.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Rive—none0/10

   No evidence of any versioned API scheme or documented deprecation policy for Rive's runtimes, editor APIs, or MCP integration; OpenAPI probes returned 404s and no changelog/versioning docs are cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   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 drawn
   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

   Rive—none0/10

   Rive's AI agent/MCP tooling is focused on generating code, view models, state machines, layouts, and animation logic — not on image generation, background removal, content-aware fill, or copy suggestions for asset creation. No evidence names any of these specific asset-chore AI features; missing for 10: image generation, background removal, content-aware fill, copy/text suggestions.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Rive~partialprobed6/10

   Rive documents an AI agent/MCP integration that generates View Models, State Machines, Layouts, Shapes and animation from prompts or via coding-agent workflows, and even an 'agent generate them with the CLI' claim on the homepage — this matches the story's spirit of prompt-driven first drafts. However, all evidence is first-party docs describing 'the first set of tools' as handling repetitive tasks rather than full end-to-end mockup generation, and there's no independent/hands-on corroboration of output quality. Missing for 10: independent or hands-on validation of AI-generated designs, clearer evidence of full mockup/layout generation (not just repetitive sub-tasks) from a single prompt.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   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

   Rive~partialclaimed6/10

   Rive documents an AI agent/MCP integration explicitly designed to let AI 'handle repetitive tasks, like creating complex View Models, State Machines with hundreds of states/layers, Layouts, Shapes, and more,' and RML provides a text-based file format enabling coding agents to script bulk edits outside the Editor. Components/instances also let one source change propagate across many instances. However, there's no independent/hands-on evidence of actual bulk-operation performance at scale, no documented API for batch scripting beyond RML/MCP, and no benchmarks or examples of large-scale bulk edits succeeding. Missing for 10: independent verification of bulk-task performance, concrete examples/benchmarks of large-scale batch operations, and a documented API/CLI for scripted bulk edits beyond the AI agent's stated purpose.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive~partialclaimed4/10

   Rive's State Machines and data-binding docs imply event-driven behavior (inputs, user actions, and data changes automatically triggering animation/state updates), and its AI Agent/MCP tooling can generate these State Machines and scripting-based behaviors programmatically. However, there's no explicit documentation of a rule-authoring system (e.g., conditional 'if event then action' automation) framed for AI-native/automation use beyond interactive animation triggers. Missing for 10: explicit rule-definition API/interface for arbitrary automation, examples of AI-native users authoring trigger-action rules, and independent confirmation beyond first-party docs.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Use scripting to create custom interactions, procedural animation, and behaviors that go beyond the built-in tools.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”

   proof ↗⚑ flag

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

   weight 1 · round to Rive
   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

   Rive~partialclaimed4/10

   Rive's Revision History provides automatic tracking of changes, previewing of past revisions, and non-destructive rollback to prior versions of a file (rive-docs-12, rive-docs-17, rive-docs-29), which covers version/rollback for the design file itself. However, the story targets 'automations' (AI-agent/MCP-driven workflows), and there is no evidence of versioning, diffing, or review specifically for AI-generated scripts, MCP actions, or automation pipelines — only generic file revision history. Missing for 10: dedicated versioning/review/rollback for AI-agent or MCP-generated automations, audit trail of agent actions, diff/compare tooling, and any independent confirmation of this workflow in practice.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   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
   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

   Rive—none0/10

   Evidence covers animation, data binding, revision history, AI/MCP tooling, and export, but there is no mention of commenting, @mentions, or thread resolution features in Rive's editor. Revision history tracks changes but is not a comment/review workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive~partialclaimed4/10

   Docs confirm multiple people can work on the same file simultaneously with all changes tracked in Revision History, implying some multiplayer support, but there is no mention of live cursors, presence indicators, or real-time instant sync mechanics that the story specifically asks for. Missing for 10: explicit live cursor/presence UI, real-time sync latency claims, independent hands-on confirmation of simultaneous editing experience.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag

Design systems

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

   weight 2 · round drawn
   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

   Rive—none0/10

   Rive is an animation/interactive-graphics tool with components, data binding, and view models, but there is no evidence of a design-tokens/variables system (colors, spacing, typography) with modes/themes applied across designs — the closest concepts (components, data binding) address reusability and runtime data, not token/theme management. Missing for 10: token or variable definitions, theme/mode switching, cross-design application of shared style values.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive✓fullclaimed8/10

   Rive's docs directly describe Components as reusable artboards where instances can be customized while changes to the source component propagate to all instances, matching the story's core requirement of variants/overrides linked to source. Missing for 10: no independent/hands-on corroboration of override behavior at scale, and no detail on variant-specific overrides beyond basic customization examples.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   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

   Rive—none0/10

   Rive's docs describe components/instances reused within a single Rive file where changes to a source component propagate to instances (rive-docs-11, rive-docs-28), but there is no evidence of a shared-library system that publishes components/styles across separate files or projects with controlled update propagation, which is the core of this story. Missing for 10: cross-file/cross-project library publishing, subscribing to a library, and controlled update notifications when a source library changes.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   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 Rive
   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

   Rive✓fullclaimed8/10

   Rive's core value prop is explicitly design-to-shippable-runtime: 'No mockups, no prototypes, no handoff... What you build in the editor is what ships in your app, game, or website' (rive-docs-23), backed by real runtime libraries that load .riv files directly into apps/games/web (rive-gh-1, rive-docs-21), reusable components/instances (rive-docs-11, rive-docs-28), and RML text representation enabling coding-agent-driven file construction (rive-docs-13, rive-docs-25, rive-docs-30). This is a genuine direct design-to-production path rather than a code-generation handoff, and MCP/AI agent tooling further bridges design and code workflows (rive-docs-9, rive-docs-19, rive-docs-27). Missing for 10: independent developer case studies confirming the 'no handoff' claim holds up in large production codebases, and clearer detail on how designers' Rive files integrate with existing component libraries/design systems in code.

   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Rive~partialprobed5/10

   Rive offers RML (text-based file format) and an MCP server that let AI/coding agents create View Models, State Machines, Layouts, and Shapes programmatically, plus open-source runtimes for playback/control — but the evidence pack does not confirm full parity with the Editor UI (e.g., no OpenAPI/REST API, no confirmation that timeline keyframing, revision history management, or component/instance authoring can be done entirely via API/CLI). missing for 10: a documented public REST/OpenAPI API surface, confirmation that all editor features (keyframe timelines, revision history, component instancing) are scriptable/API-accessible, and independent hands-on verification that AI/API workflows match UI capability.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”

   proof ↗⚑ flag

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

   weight 3 · round to Canva
   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

   Rive!disputedcontradicted4/10

   Rive documents an open, text-based file representation (RML/XML) and open-source runtimes, suggesting some data portability (rive-docs-13, rive-docs-20, rive-docs-25, rive-docs-21, rive-gh-1). However, community feedback directly contradicts a full 'export and leave' story: users report no way to export movie/video assets (rive-comm-3, rive-comm-10) and note the open-source license only covers a narrow rendering subset while the actual content-creation editor remains proprietary and subscription-locked (rive-comm-5, rive-comm-1, rive-comm-2), undermining claims of full open-format data portability. missing for 10: documented full-fidelity export to universal open formats (e.g. video/SVG/JSON), open-source editor or file-format spec, and independent confirmation that RML round-trips 100% of file data without proprietary lock-in.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   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

   Rive~partialcommunity5/10

   Rive's runtimes are documented and confirmed on GitHub as open-source libraries (rive-docs-21, rive-gh-1, rive-gh-2), giving AI-native users real source access to the rendering/runtime layer, but community evidence notes the MIT license only covers a 'rendering abstraction layer, a subset of the Rive runtime' while the Editor itself (where files are authored) remains closed-source (rive-comm-5, rive-comm-1). missing for 10: full-product open license (editor/design tool source not published), independent confirmation of license file/terms, clarity on what runtime components are excluded from the OSS layer.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   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

   Rive—none0/10

   Rive's core product is the proprietary Editor (a SaaS/desktop app); only a subset of the runtime rendering layer is open-source (MIT), and community evidence explicitly notes the editor itself cannot be self-hosted and requires the hosted tool to author content. No docs or evidence describe self-hosting the Editor or backend service.

   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   proof ↗⚑ 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
   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

   Rive—none0/10

   No evidence of a documented editor plugin/extension API, typings, or samples for building third-party editor extensions; the evidence only covers runtimes, data binding, AI agent/MCP integration, and RML scripting, none of which document an extensibility API for building/distributing editor plugins.

   ⚑ flag

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

   weight 2 · round to Canva
   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

   Rive—none0/10

   No evidence of a plugin marketplace, third-party extension ecosystem, or add-ons like icon packs, data fillers, or accessibility checkers. The evidence only covers Rive's own built-in features (components, data binding, MCP/AI agent, RML) — none of which describe an external plugin/marketplace ecosystem. Missing for 10: any mention of a plugin API, extension marketplace, or third-party-built add-ons.

   ⚑ flag

Pricing

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

   weight 1 · round drawn
   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

   Rive—none0/10

   The evidence pack contains only product/docs content about Rive's features (animation, data binding, AI agent, MCP) and community discussion referencing informal price points ($25-$39/month) but no published pricing page, seat-type breakdown, tier comparison, or explicit AI-feature gating documentation.

   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Rive—none0/10

   No evidence describes what the free tier includes for editor/collaboration access; the only relevant community signal explicitly states that basic solo-dev animation work requires a paid subscription ($25-39/month), suggesting the free tier is not sufficient for real design work.

   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”
   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   proof ↗⚑ 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 Rive
   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

   Rive✓fullcommunity8/10

   Rive's docs explicitly describe building interactive experiences responding to user input, screen size, scrolling, and application state (rive-docs-4), state machines/timelines/keyframes (rive-docs-3), and real-time data binding so animations update live (rive-docs-5, rive-docs-15, rive-docs-22, rive-docs-24) — directly matching the story's states/conditions/variables/scroll-effect prototyping needs. Community evidence corroborates real-world adoption for production-grade interactive UI/UX work (rive-comm-4, rive-comm-7), and Rive's own positioning ('no mockups, no prototypes... the real thing', rive-docs-16/23) reflects this design intent. Missing for 10: independent hands-on verification specifically of scroll-triggered effects and variable/condition-driven prototypes beyond vendor docs.

   • [claimed-docs] “Bring your designs to life with timelines, keyframes, and smooth interpolation.”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Connect animations, text, colors, layouts, and other properties to real-time data.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “I've been pushing over the past six months or so for multiple clients... to adopt Rive over Lottie and other past solutions, as I think it's…”
   • [community] “Truthfully the program they have looks fantastic at empowering UI/UX designers to do more with games... the workflow of this tool is definit…”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   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

   Rive~partialclaimed5/10

   Rive's State Machines and interaction docs (rive-docs-4, rive-docs-22, rive-docs-24) support building input-driven, trigger/transition-based interactivity without code, and rive-docs-16/23 frame the tool as skipping separate 'prototype' handoff entirely. However there is no evidence of a Figma-style multi-screen/overlay prototyping paradigm (linking distinct screens, overlay layers, click-through flows across artboards) — Rive's interactivity is scoped to state machines within/across components rather than an explicit screen-flow prototyping mode. Missing for 10: evidence of multi-screen linking, overlay/modal wiring, and click-through flow prototyping across separate artboards/screens.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”

   proof ↗⚑ flag

Canvas

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

   weight 2 · round to Rive
   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

   Rive~partialclaimed5/10

   Rive's docs repeatedly reference "responsive layouts" and building interfaces that respond to screen size (rive-docs-1, rive-docs-4, rive-docs-9, rive-docs-18, rive-docs-26), and the AI tooling explicitly generates "Layouts" as an artboard-level construct (rive-docs-10). However, no evidence details the specific mechanics of auto layout, constraints, or grid systems the way Figma-style tools describe them. Missing for 10: explicit documentation of constraint-based resizing rules, grid systems, or auto-layout algorithms, and independent/hands-on confirmation that layouts flex like real UI frameworks.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive!disputedcontradicted3/10

   Rive's docs market it as a full design-to-ship tool ('design, animate, and code in one place... no mockups, no prototypes, no handoff') and mention vector graphics and components, but there is no documentation of boolean operations, precise alignment/snapping tools, or advanced path editing. A hands-on community comment directly contradicts the 'professional vector tools' claim, calling the drawing toolset just 'a pen and a couple of basic shapes' and comparing inefficient pen-only workflows unfavorably to real illustration tools. missing for 10: boolean operations, alignment/snap tooling, path-editing depth, and any rebuttal to the community criticism of basic drawing tools.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “Looks kinda interesting but I am not gonna touch anything that thinks an acceptable set of drawing tools is 'pen and a couple of basic shape…”

   proof ↗⚑ flag

Files

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

   weight 2 · round to Canva
   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

   Rive—none0/10

   Rive's documentation focuses on exporting .riv files for runtime playback across platforms (web, mobile, games) rather than static production assets like PNG/SVG/PDF with per-layer presets, scales, or slices; no such export presets are described anywhere in the evidence. Community feedback explicitly confirms this gap — one user complains 'it's so insane they don't offer any way to export movie files' and another asks 'can I export video assets with this!?' — indicating the tool lacks traditional multi-format asset export entirely.

   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   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 to Rive
   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

   Rive!disputedcontradicted4/10

   Rive documents RML (a text-based/XML representation of Rive files) and open-source runtimes that can load/parse .riv files (rive-docs-13/20/25/30, rive-gh-1/3), suggesting some portability outside the editor. However, community evidence directly disputes this: the open-source runtime is described as only a rendering/playback layer, and actually authoring or building Rive content still requires the proprietary, paid Rive Editor (rive-comm-5), undercutting claims of full format openness/portability. Missing for 10: a public, versioned .riv binary spec independent of RML, third-party tools that can author/edit .riv files without the vendor's editor, and confirmation that RML round-trips losslessly with the binary format.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Rive—none0/10

   Evidence shows only the rendering runtime is open-source (rive-docs-21, rive-gh-1/2/3), while the Editor itself is a hosted SaaS product requiring Rive's cloud service—there is no documentation of a self-hostable full design platform. Community discussion explicitly confirms this gap, noting the MIT license covers only 'a subset of the Rive runtime that requires the Rive Editor to build content for' (rive-comm-5), meaning the actual design/editing platform cannot be self-hosted.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   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

   Rive~partialclaimed6/10

   Rive's docs confirm automatic revision tracking, non-destructive restore, and the ability to select and edit a prior revision (rive-docs-12, rive-docs-17, rive-docs-29), which covers 'restore any earlier state.' However there is no evidence of naming/labeling milestones or a compare/diff view between versions. Missing for 10: named milestone/labeling capability, side-by-side or diff comparison between revisions, independent corroboration of the restore workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag