Framer vs Spline

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

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

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

   proof ↗⚑ flag

   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

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

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Framer
   Framer~partialclaimed7/10

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

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

   proof ↗⚑ flag

   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

Agent access

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

   weight 2 · round to Spline
   Framer✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Framer
   Framer~partialprobed3/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Spline
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Spline
   Framer~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Framer—none0/10

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

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

   proof ↗⚑ flag

   Spline—none0/10

   Evidence shows Spline offers an MCP server for connecting AI coding tools to the editor, but there is no mention of scoped or least-privilege API credentials, API keys with permission scopes, or any access-control mechanism for issuing restricted agent credentials. Missing for 10: any documentation of credential/token scoping, permission levels, or least-privilege API key issuance for agents.

   • [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…”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Framer~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Spline
   Framer—none0/10

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

   ⚑ flag

   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

Agentic features

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

   weight 2 · round drawn
   Framer~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Framer✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Framer✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

Ai

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

   weight 1 · round drawn
   Framer~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Framer
   Framer✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Framer
   Framer~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Spline
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 1 · round to Framer
   Framer✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

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

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

   ⚑ flag

   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

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

   weight 3 · round to Spline
   Framer—none0/10

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

   ⚑ flag

   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

Design systems

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

   weight 2 · round drawn
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Spline
   Framer~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Spline
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Framer—none0/10

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

   ⚑ flag

   Spline—none0/10

   Spline's docs describe code export as full-scene exports (Vanilla JS, Three.js, React, Next.js, react-three-fiber) and a Code API for developers, but there is no evidence of a dev-handoff/inspect mode that lets a non-editor viewer inspect a specific layer for measurements, styles, assets, or CSS/iOS/Android snippets without holding an editor seat.

   • [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] “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”

   proof ↗⚑ flag

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

   weight 2 · round to Framer
   Framer~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Spline
   Framer—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Framer—none0/10

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

   ⚑ flag

   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

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Framer—none0/10

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

   ⚑ flag

   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

Plugins

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

   weight 2 · round to Framer
   Framer~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Framer
   Framer~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

Pricing

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

   weight 1 · round to Spline
   Framer—none0/10

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

   ⚑ flag

   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

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

   weight 2 · round to Spline
   Framer—none0/10

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

   ⚑ flag

   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

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

   weight 2 · round drawn
   Framer—none0/10

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

   ⚑ flag

   Spline—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls; Spline docs discuss cloud storage, multiplayer, exports and MCP but never a data-region choice. missing for 10: any mention of region/residency options, data center choice, or compliance certifications tied to storage location.

   ⚑ flag

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

   weight 3 · round drawn
   Framer—none0/10

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

   ⚑ flag

   Spline—none0/10

   No evidence in the pack addresses AI-training data opt-out, privacy settings, or data usage policies for model training; the docs focus entirely on design/collaboration/AI-generation features with no mention of privacy controls or training data exclusion.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Framer—none0/10

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

   ⚑ flag

   Spline—none0/10

   The evidence pack contains no mention of data retention policies, deletion controls, data export for compliance, or privacy/GDPR settings for AI-native users; it covers only design, collaboration, export, and MCP/AI features. Missing for 10: any documentation of data retention settings, account/file deletion controls, or privacy compliance mechanisms.

   ⚑ flag

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

   weight 2 · round drawn
   Framer—none0/10

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

   ⚑ flag

   Spline—none0/10

   No evidence in the pack addresses telemetry, analytics, or usage tracking opt-out settings for Spline; the docs cover design features, MCP, exports, and collaboration but nothing about privacy/tracking controls. This is a fair axis for a cloud-based SaaS design tool, so absence of evidence yields 'none'.

   ⚑ flag

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

   weight 1 · round to Spline
   Framer!disputedcontradicted6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Spline
   Framer~partialcommunity4/10

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

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

   proof ↗⚑ flag

   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

Canvas

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

   weight 2 · round to Framer
   Framer~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Spline
   Framer—none0/10

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

   ⚑ flag

   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

Files

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

   weight 2 · round drawn
   Framer—none0/10

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

   ⚑ flag

   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

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

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

   ⚑ flag

   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

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

   weight 2 · round drawn
   Framer—none0/10

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

   ⚑ flag

   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

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

   weight 2 · round to Spline
   Framer~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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