Spline 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 drawn
   Spline✓fullprobed8/10

   Spline ships a dedicated MCP Server (bundled in desktop app) that lets Claude, Cursor, Codex, VS Code, Antigravity and ChatGPT drive the live editor to create/modify designs, plus a write-capable Code API for programmatic scene manipulation and webhooks/Real-time API for external event-driven updates. This goes beyond read-only access into genuine programmatic creation/modification. Missing for 10: independent hands-on validation of the MCP server's write actions and no public OpenAPI spec was found (openapi probe 404s), so full API surface is only documented, not independently verified.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “the desktop app gives you a few things the browser can't: **tabs** for working across several files, **system fonts**, and **MCP** support”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “Spline works fully in the browser, but the desktop app gives you a few things the browser can't: **tabs** for working across several files, …”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   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 Spline
   Spline~partialprobed4/10

   Spline documents multiple export/programmatic surfaces (export-as-code for Vanilla JS/Three.js/React/Next.js/r3f, self-hosted ZIP export, Code API, Real-time API, webhooks) and an MCP server that lets agents like Claude/Cursor drive the editor, but none of the docs explicitly describe an agent invoking a screenshot/image render or export action through these interfaces — the MCP surface is framed as scene building/editing, not export/rendering. Missing for 10: explicit MCP or API tool for triggering exports/screenshots/renders programmatically, and independent confirmation this works end-to-end for an agent.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   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 Spline
   Spline~partialprobed6/10

   Spline ships an official MCP server bundled with the desktop app that connects Claude, Cursor, Codex, Antigravity and other MCP clients directly to the open editor, and separately offers a Code API, Real-time API and code export (React/Next.js/Three.js/react-three-fiber) that could let an agent read variables and scene structure to implement designs. However the MCP server's documented purpose is to let AI clients drive/edit the Spline scene ('straight into your open editor tab'), not explicitly to pull frames, screenshots, or component mappings as design-context for an external implementation — that specific dev-mode-style extraction flow is not evidenced. Missing for 10: explicit support for screenshot export via MCP/API, frame-level context retrieval, and documented component-mapping extraction for code implementation.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   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 Spline
   Spline✓fullprobed9/10

   Spline has a verified llms.txt at docs.spline.design/llms.txt (HTTP 200 probe) plus .md-suffixed doc pages that render clean markdown for agent consumption, confirming genuine agent-oriented docs infrastructure. missing for 10: independent third-party confirmation that agents actually consume these docs successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.spline.design/llms.txt # Spline Documentation ## Docs - [Getting Started](https://docs.spline.des…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.spline.design/basics/what-is-spline.md # What is Spline? (/basics/what-is-spline) Spline is a web…”
   • [claimed-docs] “How Spline compares to traditional 3D tools like Blender, Maya and Cinema 4D.”

   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 Rive
   Spline—none0/10

   Spline is documented purely as a browser/desktop GUI editor with a multiplayer, real-time canvas; its MCP server explicitly requires the desktop app with 'your open editor tab' running interactively, and no CLI, headless render mode, or CI-triggerable build/export process is documented anywhere in the evidence pack. Webhooks and the Real-time API only affect published/runtime scenes, not the design-time editor pipeline, so there is no path to running Spline itself headlessly in automation.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”

   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
   Spline—none0/10

   All evidence describes Spline shipping an MCP *server* (docs-13, docs-25, docs-36, docs-53) that external MCP clients like Claude/Cursor/Codex connect to — the reverse of this story, which asks whether a user can plug external MCP servers into Spline so its own AI agent can use their tools. No evidence shows Spline acting as an MCP client or consuming third-party MCP tool servers.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”

   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 drawn
   Spline✓fullprobed8/10

   Spline documents an official MCP server bundled in the desktop app that connects Claude, Cursor, Codex, VS Code, Antigravity, and ChatGPT directly to the editor, requiring no separate install/config. This is a clear first-party MCP server offering with dedicated docs. Missing for 10: independent/hands-on community corroboration of the MCP server actually working, and no detail on the specific tools/capabilities exposed via the server.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   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 userDrive the product through a documented public API

   weight 3 · round to Rive
   Spline~partialprobed7/10

   Spline documents several external-facing interfaces an AI-native user could drive: the Real-time API and Webhooks for event-driven external integration, a Code API for web to control published scenes from external code/UI, and an MCP Server that lets AI coding agents (Claude, Cursor, Codex) manipulate the editor directly. These are genuine documented, public-facing APIs beyond just manual UI use. missing for 10: a formal REST/OpenAPI specification (probe explicitly found no openapi.json/swagger.json at any candidate path), and independent/hands-on corroboration that these APIs work reliably outside vendor docs.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   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

6. ai-native userBuild against official SDKs

   weight 2 · round to Rive
   Spline~partialprobed6/10

   Spline documents a Code API and multiple official code-export targets (Vanilla JS, Three.js, React, Next.js, react-three-fiber) plus a self-hosted runtime export, which functions as an SDK-like integration surface for developers (spline-docs-6, spline-docs-12, spline-docs-17, spline-docs-8). However, a live probe for a formal OpenAPI/SDK spec returned 404s, and there's no independent developer corroboration of SDK usage or versioned package docs beyond the docs site. Missing for 10: dedicated SDK/package documentation (e.g. npm SDK docs), OpenAPI/API reference, and third-party hands-on confirmation of building against these SDKs.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   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

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to Spline
   Spline✓fullclaimed7/10

   Spline docs explicitly document a Webhooks feature that allows listening for and responding to external events, triggering actions, updating variables, and reacting to data sent from external sources — directly matching the story. However, this is first-party documentation only with no independent/hands-on corroboration or detail on subscription mechanics (event types, payload schema, delivery guarantees). Missing for 10: independent verification of webhook reliability, detailed event-type/payload documentation, hands-on community testing.

   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”

   proof ↗⚑ 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 Spline
   Spline~partialclaimed4/10

   Spline offers webhooks and a Real-time API that let a published scene 'automatically trigger actions, update variables, and react to data sent from external sources' without a person driving it (spline-docs-9, spline-docs-10, spline-docs-26), which is a form of event-driven automation running unattended. However, this is scene-level reactivity to external events, not a general-purpose scheduled/autonomous agent workflow — the AI Agent and MCP integrations require an open editor tab and active AI-tool session (spline-docs-13, spline-docs-25) rather than running independently in the background. Missing for 10: evidence of scheduled/cron-like autonomous tasks, independent confirmation of webhook automation working in practice, and any agentic workflow that persists without an open editor session.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”

   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
   Spline✓fullclaimed7/10

   Spline ships a built-in AI Agent that autonomously builds and edits 3D scenes ('describe what you want and it does the work through the editor itself — creating objects, setting up materials and lighting, animating, wiring interactivity') and a parallel Hana AI Agent for 2D screens, both directly matching the delegated-task story. Missing for 10: independent/hands-on verification of the agent's real-world reliability and scope beyond first-party docs.

   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “Hana's AI Agent designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interactions.”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   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 Spline
   Spline✓fullclaimed8/10

   Spline's AI Agent lets users describe what they want in natural language and the editor builds objects, materials, lighting, animation, and interactivity accordingly (spline-docs-3, spline-docs-20, spline-docs-40), and Hana's AI Agent similarly designs UI screens from natural-language descriptions (spline-docs-21, spline-docs-39, spline-docs-54). AI texture generation also works by typing descriptions (spline-docs-4, spline-docs-28). This is reinforced by an MCP server enabling natural-language driven control from external AI clients like Claude/Cursor (spline-docs-13, spline-docs-36). Missing for 10: independent/hands-on user reports confirming natural-language command reliability and breadth of coverage beyond first-party docs.

   • [claimed-docs] “describe what you want and the 3D editor builds it: objects, materials, lighting, animation, interactivity.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “Use Artificial Intelligence to generate textures like grass, concrete, wood, ceramic, and patterns just by typing!”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”

   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
   Spline—none0/10

   Spline documents several APIs (Code API, Real-time API, webhooks) but the evidence pack shows no interactive API reference with runnable examples — a probe for OpenAPI/swagger specs returned 404 on all candidate paths, and the docs are plain markdown descriptions rather than an interactive sandbox.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”

   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 drawn
   Spline—none0/10

   A direct probe for OpenAPI/swagger specs at common paths returned 404 across all candidates, and no documentation references a downloadable machine-readable API spec; Spline offers a Real-time API and Code API but no OpenAPI equivalent is evidenced.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   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
   Spline—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the OpenAPI probe returned 404s across all candidate paths, and no docs mention version numbers, changelogs, or deprecation timelines for the Real-time API, Code API, or MCP server.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   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 to Spline
   Spline~partialclaimed3/10

   Spline documents built-in AI features—AI-generated textures via text prompts and an AI Agent/Hana that builds/edits 3D scenes and screens—which is a form of in-editor generative asset creation, but there's no evidence of background removal, content-aware fill, or AI copy/text suggestions inside the editor. missing for 10: background removal, content-aware fill, copy/text suggestions, general image asset generation beyond textures.

   • [claimed-docs] “Use Artificial Intelligence to generate textures like grass, concrete, wood, ceramic, and patterns just by typing!”
   • [claimed-docs] “Use Artificial Intelligence to generate textures like **grass**, **concrete**, **wood**, **ceramic**, and **patterns** just by typing!”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   proof ↗⚑ 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 to Spline
   Spline✓fullclaimed7/10

   Spline documents two AI Agents that generate designs from natural-language prompts: the 3D AI Agent creates objects, materials, lighting, animation and interactivity from a description, and Hana's AI Agent designs full 2D screens (layout, type, colour, effects, states) from a text description, which can then be edited by hand. This directly matches the story of generating first drafts/mockups from a prompt. Missing for 10: independent/hands-on verification of the AI Agent's actual output quality, and no third-party reviews or demos confirming real-world reliability of these AI generation features.

   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “Hana's AI Agent designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interactions.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself”

   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 Rive
   Spline—none0/10

   Spline's docs describe single-scene editing, MCP/Code API/webhook integrations, and AI generation features, but nothing indicates batch or bulk processing across many objects, scenes, or files at once (e.g., no scripting loop API, no bulk export/import, no multi-file automation mentioned).

   ⚑ 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 Spline
   Spline✓fullclaimed7/10

   Spline's states/events/actions system, webhooks, and Real-time API let users define rules that trigger actions automatically on events (e.g., 'automatically trigger actions, update variables, and react to data sent from external sources'), which is core automation-depth functionality. missing for 10: independent/hands-on verification of event-rule automation in practice, and more detail on the breadth/complexity of conditional logic supported beyond docs claims.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”

   proof ↗⚑ 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 Spline
   Spline~partialclaimed5/10

   Spline's Version History lets users preview, recover, and manually save previous file states, which would cover the interactivity/automation logic (events, actions, webhooks) embedded in a scene, but this is a whole-file history feature, not a dedicated review/diff mechanism for automations specifically, and no evidence of granular change review or approval workflows exists. missing for 10: automation-specific diffing/review UI, branching or approval workflow, independent confirmation of rollback reliability for complex automations.

   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files. This feature helps you track changes, recover previou…”
   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   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 Spline
   Spline~partialclaimed4/10

   Docs confirm real-time multiplayer editing and that users can 'give feedback in place, the way they would in a 2D design tool,' implying some in-file commenting, but there is no mention of @mentioning teammates or resolving comment threads. missing for 10: explicit mention/tagging of teammates, ability to resolve/close comment threads, dedicated commenting UI documentation.

   • [claimed-docs] “Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “It's multiplayer. Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”

   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 Spline
   Spline✓fullclaimed8/10

   Multiple first-party docs consistently describe Spline as "multiplayer from the ground up," cloud-hosted files enabling several people to edit the same file simultaneously with in-place feedback, similar to 2D design tools — directly matching the story. Missing for 10: explicit mention of live cursors specifically, and no independent/hands-on corroboration of real-time sync quality at scale.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “It's multiplayer. Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “Spline is two editors that share the same interactivity model, the same real-time collaboration, and the same publishing pipeline.”

   proof ↗⚑ 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
   Spline—none0/10

   Spline's docs mention 'variables and data' only in the context of real-time API/webhooks event data, not design tokens for color, spacing or typography, and the only 'theme' feature found is the editor's own Dark/Light/System UI theme, not a token system applied across a designer's own scenes. No evidence shows reusable style tokens with modes/themes propagated across designs.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Spline supports **Dark**, **Light**, and **System** themes so you can customize the interface to your preference.”

   proof ↗⚑ 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
   Spline~partialclaimed4/10

   Spline docs confirm a Components system where reusable objects propagate changes from a main component to all instances (spline-docs-5), which covers the 'linked to source' part of the story. However, there is no evidence of a variants system (multiple named states of a component) or per-instance override capability that persists while staying linked, as seen in dedicated design tools. Missing for 10: documented variants/property sets per component, explicit per-instance override UI, and evidence of overrides surviving source updates.

   • [claimed-docs] “Components are objects that can be reused multiple times throughout your scene and whenever there are changes made to the main component all…”

   proof ↗⚑ 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 Spline
   Spline~partialclaimed4/10

   Spline documents component reuse where instances update when the main component changes (spline-docs-5), and pricing mentions a 'Team Library' feature (spline-docs-33), implying some shared-library capability across a team. However, there's no documentation detailing publishing components/styles across separate files or projects, or how updates propagate/are controlled at that scope. Missing for 10: cross-file/cross-project library publishing workflow, versioned/controlled update mechanism, and any independent confirmation of Team Library behavior.

   • [claimed-docs] “Components are objects that can be reused multiple times throughout your scene and whenever there are changes made to the main component all…”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   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
   Spline✓fullclaimed7/10

   Spline documents direct design-to-code export in multiple production-ready formats (Vanilla JS, Three.js, React, Next.js, react-three-fiber), plus a Code API for wiring exported scenes into existing codebases, a self-hosted ZIP export bundling assets/runtime, and a native <spline-viewer> web component for drop-in embedding — all clearly aimed at shipping designed 3D/2D scenes into real production code. Missing for 10: independent/hands-on verification that exported code is production-quality and maintainable, and explicit component-to-code sync (e.g., design system tokens/components mapped 1:1 to code components) beyond scene-level export.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: * **Vanilla JS**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “`<spline-viewer>` is a native HTML web component and can be used with most web builders, frameworks, or browsers.”

   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
   Spline~partialprobed5/10

   Spline offers real API-like surfaces for AI-native workflows — a Code API for runtime object/property control (spline-docs-6, -17), a Real-time API and webhooks for external data/events (spline-docs-9, -10, -26), and notably an official MCP server that lets AI clients like Claude/Cursor/Codex drive the live editor tab directly (spline-docs-13, -36, -53) plus an AI Agent that can create objects, materials, lighting and interactivity through the editor (spline-docs-20, -40, -55). However, probing for a formal REST/OpenAPI spec returned 404s across all candidate paths (spline-probe-3), and the documented APIs are scoped to runtime manipulation/events, not full parity with the UI's modeling toolset (booleans, hair systems, physics, gaussian splatting, materials library) — so full UI-equivalent API coverage is not evidenced. missing for 10: a documented comprehensive API/SDK exposing full scene-authoring parity (modeling, materials, physics, animation) rather than just runtime triggers/MCP-driven editor control, and independent confirmation of API completeness.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   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 Spline
   Spline✓fullclaimed7/10

   Spline documents self-hosted export (full project, assets, and runtime as a self-contained ZIP) and code export in multiple open web formats (Vanilla JS, Three.js, React, Next.js, react-three-fiber), giving users a way to take their scene data out of the platform entirely rather than being locked into a proprietary cloud-only format. Missing for 10: no evidence of exporting to standard interchange 3D formats (e.g., glTF/OBJ), no independent/hands-on confirmation that self-hosted exports are truly complete and portable, and no mention of exporting non-visual metadata (variables, version history) alongside the scene.

   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   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
   Spline—none0/10

   Spline is a closed, proprietary commercial design tool; nothing in the evidence pack mentions an open-source license or publicly available source code for the core product (only exported project assets can be self-hosted, which is not the same as open-sourcing the tool's source).

   ⚑ 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
   Spline—none0/10

   Spline is an inherently cloud/multiplayer SaaS editor ('files live in the cloud', 'multiplayer from the ground up') with no evidence of a self-hostable core editor. The 'Self-Hosted' feature only lets users export a finished scene/runtime as a static ZIP for embedding elsewhere — it does not let anyone run the Spline design tool itself on their own infrastructure.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”

   proof ↗⚑ 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 drawn
   Spline—none0/10

   Spline documents a Code API, MCP server, webhooks, and export pipelines for integrating exported scenes into external apps, but there is no evidence of a documented plugin/extension API (with typings and samples) for building and distributing extensions to the Spline editor itself, and an OpenAPI/SDK probe returned 404s. Missing for 10: a documented editor plugin SDK, typings/type definitions for plugin development, and sample plugin code or a plugin marketplace/distribution mechanism.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   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 drawn
   Spline—none0/10

   No evidence of a plugin community, marketplace, or third-party extensions (icons, data fillers, accessibility checkers) for Spline; the evidence only covers Spline's own built-in features (AI tools, MCP server, code export, materials library).

   ⚑ 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 to Spline
   Spline~partialclaimed2/10

   Only one evidence item references the pricing page at all, and it's a bare fragment listing a few feature bullets (code/self-hosted export, version history, team library) with no visible seat types, tier names, or explicit AI-feature gating breakdown. Missing for 10: documented tier names/pricing, seat-type definitions, explicit AI feature gating per tier, and any independent corroboration of the pricing page's clarity.

   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   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 to Spline
   Spline~partialclaimed3/10

   Docs describe Spline as 'multiplayer from the ground up' with cloud-based files that several people can edit at once, suggesting collaboration is core to the product rather than gated behind a paid seat, but the evidence pack has no explicit free-tier pricing page detail confirming seat limits, viewer/editor caps, or whether real-time collaboration is unrestricted on the free plan. The one pricing-page snippet (spline-docs-33) lists Code/self-hosted exports, version history, and Team Library without clarifying tier boundaries. missing for 10: explicit free-tier plan page detailing seat/collaborator limits, independent user reports confirming free-tier collaboration works in practice.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ 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 drawn
   Spline✓fullclaimed8/10

   Spline's docs strongly evidence advanced prototyping behavior: states/events/actions interaction model, variables and real-time API, webhooks for event-driven reactions, animation, multi-scene transitions, physics, and even code/HTML embedding for custom logic — all built to make prototypes feel like real products. Missing for 10: independent hands-on validation of complex behavior chains (scroll-driven effects specifically) and no dedicated 'scroll trigger' doc beyond general events/actions system.

   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “You can create multiple scenes within the same Spline file... It's possible to transition between scenes with the Events system by using a S…”
   • [claimed-docs] “On Spline you can create different types of physics simulations, each object can be adjusted to react to gravity and collision forces.”
   • [claimed-docs] “A file can carry one HTML document — markup, CSS and JavaScript — that the editor renders in a sandboxed iframe layered exactly over the 3D …”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”

   proof ↗⚑ 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 Spline
   Spline~partialclaimed6/10

   Docs confirm no-code interactivity via states/events/actions (spline-docs-31) and multi-scene transitions via the Events system's Scene Transition action (spline-docs-61), which directly supports triggers and transitions for prototyping. However, 'overlays' are only evidenced via the Code tab feature, which requires writing HTML/CSS/JS (spline-docs-11/24), contradicting the 'no code required' framing for that specific element, and there is no dedicated hands-on or independent account of designers building full clickable multi-screen prototypes end-to-end. Missing for 10: a no-code overlay/layering mechanism, and independent/hands-on evidence of a complete click-through prototype workflow across screens.

   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”
   • [claimed-docs] “You can create multiple scenes within the same Spline file... It's possible to transition between scenes with the Events system by using a S…”
   • [claimed-docs] “A file can carry one **HTML document** — markup, CSS and JavaScript — that the editor renders in a sandboxed iframe layered exactly over the…”
   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”

   proof ↗⚑ 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
   Spline—none0/10

   Spline's docs cover 3D modeling, materials, animation, multiplayer, AI generation, and code export, and even mention a 2D canvas (Hana) for interfaces, but nowhere is there mention of auto layout, constraints, or responsive grid systems that would let frames resize like real UI layouts. Missing for 10: any documentation of auto-layout, constraint-based resizing, or grid systems for frames.

   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   proof ↗⚑ 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 Spline
   Spline~partialclaimed5/10

   Docs confirm a pen tool for custom 2D shapes (spline-docs-43), boolean operations (Union/Subtract/Intersect) for objects (spline-docs-60), a dedicated 2D canvas with vector networks for interfaces (spline-docs-38), and extrusion turning 2D shapes into 3D (spline-docs-42) — core vector-editing primitives are present. However, there's no documentation of precise alignment/distribution tools, grids, or snapping, and no independent/hands-on evidence validating these tools for serious interface design work versus its primary 3D focus. Missing for 10: alignment/snapping tooling documentation, path-editing depth (e.g., bezier handle controls), independent corroboration of professional UI design usage.

   • [claimed-docs] “The pen tool enables you to create custom 2D shapes in the 3D space. It works in a familiar way to other 2D or UI design tools.”
   • [claimed-docs] “There are 3 different Boolean Operations that you can apply to a set of selected 3D objects: Union ... Subtract ... Intersect”
   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”
   • [claimed-docs] “Although 2D objects don't have a depth parameter, they can quickly become 3D using a modeling operation called **Extrusion**.”

   proof ↗⚑ 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 drawn
   Spline—none0/10

   Spline's documented export options are all code/runtime based (Vanilla JS, Three.js, React, Next.js, react-three-fiber, self-hosted ZIP, spline-viewer web component) with no mention of PNG/SVG/PDF raster/vector asset export, per-layer presets, scales, or slices anywhere in the evidence pack.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   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 Spline
   Spline~partialclaimed5/10

   Spline's native .spline file format itself is never documented as open or given a public schema; instead portability is achieved indirectly via export mechanisms — code export to Vanilla JS/Three.js/React/Next.js/react-three-fiber, a self-hosted ZIP with the runtime, and a Code API — which let designs be used outside the editor without exposing/documenting the native format. missing for 10: an open/published spec for the native .spline file format, third-party tooling that reads/writes it directly, independent confirmation that exported code is a full fidelity substitute for the file itself.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”

   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
   Spline—none0/10

   Spline is a cloud-based, closed-source SaaS design tool; the only 'self-hosted' feature documented is exporting a finished 3D scene as a self-contained ZIP for use in your own web app, not self-hosting the design editor/platform itself. There is no evidence of an open-source license, on-prem installer, or self-hostable server for the full editor.

   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”
   • [claimed-docs] “Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”
   • [claimed-docs] “It's web-based. Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”

   proof ↗⚑ 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 drawn
   Spline~partialclaimed6/10

   Docs confirm a Version History feature that lets users preview all saved versions, track changes, and restore/recover earlier file states, plus manually save new versions ([spline-docs-15],[spline-docs-29],[spline-docs-33]). However, there is no evidence of explicitly naming/labeling milestones or a side-by-side compare view between versions. Missing for 10: explicit naming/labeling of milestone versions, a diff/compare UI between versions, independent hands-on confirmation of restore workflow.

   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files. This feature helps you track changes, recover previou…”
   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

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