Install
npm install @splinetool/runtimeTry itExperimental
See what an agent can do with Spline before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -sL https://docs.spline.design/llms.txt | head -3recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agent design — stories about agent design in this arenaAgent designevidence →
Stories about agent design in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai design — stories about ai design in this arenaAi designevidence →
Stories about ai design in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Collaboration multiplayer — stories about collaboration multiplayer in this arenaCollaboration multiplayerevidence →
Stories about collaboration multiplayer in this arena
Components design systems — stories about components design systems in this arenaComponents design systemsevidence →
Stories about components design systems in this arena
Dev handoff — stories about dev handoff in this arenaDev handoffevidence →
Stories about dev handoff in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Plugins extensibility — stories about plugins extensibility in this arenaPlugins extensibilityevidence →
Stories about plugins extensibility in this arena
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Prototyping — stories about prototyping in this arenaPrototypingevidence →
Stories about prototyping in this arena
Vector editing — stories about vector editing in this arenaVector editingevidence →
Stories about vector editing in this arena
Versioning export — stories about versioning export in this arenaVersioning exportevidence →
Stories about versioning export in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Spline stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent design — stories about agent design in this arenaAgent design
Stories about agent design in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~7/10
unlocks → Scoped API keys · Machine-readable spec · Versioning policy · Headless / CI · A documented plugin API with typings and samples lets me build and distribute my own editor extensions · Extend the editor from a large plugin community or marketplace — icons, data fillers, accessibility checkers, and more
Subscribe to events via webhooks
✓7/10
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
n/an/a
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓7/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~4/10
Ai design — stories about ai design in this arenaAi design
Stories about ai design in this arena
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Collaboration multiplayer — stories about collaboration multiplayer in this arenaCollaboration multiplayer
Stories about collaboration multiplayer in this arena
Components design systems — stories about components design systems in this arenaComponents design systems
Stories about components design systems in this arena
Design systems
Dev handoff — stories about dev handoff in this arenaDev handoff
Stories about dev handoff in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Openness
Self-host the core product
—0/10
Export all of my data in open formats and leave
✓7/10
unlocks → Export production assets — PNG, SVG, PDF, and more — with per-layer presets, scales, and slices · Self-host the full design platform on my own infrastructure under an open-source license
Do everything through the API that I can do in the UI
~5/10
Read the product's source under an open license
—–
Plugins extensibility — stories about plugins extensibility in this arenaPlugins extensibility
Stories about plugins extensibility in this arena
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Prototyping — stories about prototyping in this arenaPrototyping
Stories about prototyping in this arena
Vector editing — stories about vector editing in this arenaVector editing
Stories about vector editing in this arena
Versioning export — stories about versioning export in this arenaVersioning export
Stories about versioning export in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 7/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | n/a | untested | none yet | |
My whole team can edit the same file simultaneously with live cursors and instant sync C Collaboration | designer | Collaboration multiplayer — stories about collaboration multiplayer in this arenaCollaboration multiplayer | 3 | full | 8/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | full | 7/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | full | 7/10 | Cclaimed | |
My coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design C Agent ops | ai-native user | Agent design — stories about agent design in this arenaAgent design | 3 | partial | 6/10 | Tprobed | |
I get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design work C Canvas | designer | Vector editing — stories about vector editing in this arenaVector editing | 3 | partial | 5/10 | Cclaimed | |
Build reusable components with variants and per-instance overrides that stay linked to their source C Design systems | designer | Components design systems — stories about components design systems in this arenaComponents design systems | 3 | partial | 4/10 | Cclaimed | |
Inspect any layer and get measurements, styles, assets, and code snippets (CSS/iOS/Android) without an editor seat G Handoff | developer | Dev handoff — stories about dev handoff in this arenaDev handoff | 3 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
An agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them C Agent ops | ai-native user | Agent design — stories about agent design in this arenaAgent design | 2 | full | 8/10 | Tprobed | |
Designs map to production code — component-to-code mappings or direct design-to-code output I can actually ship C Handoff | developer | Dev handoff — stories about dev handoff in this arenaDev handoff | 2 | full | 7/10 | Cclaimed | |
Generate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually produces C Ai | designer | Ai design — stories about ai design in this arenaAi design | 2 | full | 7/10 | Cclaimed | |
Full version history lets me name milestones, compare, and restore any earlier state of a file C Files | designer | Versioning export — stories about versioning export in this arenaVersioning export | 2 | partial | 6/10 | Cclaimed | |
Wire screens into clickable prototypes with triggers, transitions, and overlays — no code required C | designer | Prototyping — stories about prototyping in this arenaPrototyping | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
An agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface C Agent ops | ai-native user | Agent design — stories about agent design in this arenaAgent design | 2 | partial | 4/10 | Tprobed | |
Comment directly on designs, mention teammates, and resolve threads so review happens in the file, not in email C Collaboration | product manager | Collaboration multiplayer — stories about collaboration multiplayer in this arenaCollaboration multiplayer | 2 | partial | 4/10 | Cclaimed | |
Shared libraries publish components and styles across files and projects, with controlled updates when the source changes C Design systems | designer | Components design systems — stories about components design systems in this arenaComponents design systems | 2 | partial | 4/10 | Cclaimed | |
The free tier supports real design work — usable editor and collaboration without a paid seat G Pricing | designer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 2 | partial | 3/10 | Cclaimed | |
A documented plugin API with typings and samples lets me build and distribute my own editor extensions C Plugins | developer | Plugins extensibility — stories about plugins extensibility in this arenaPlugins extensibility | 2 | none | 0/10 | ||
Export production assets — PNG, SVG, PDF, and more — with per-layer presets, scales, and slices C Files | designer | Versioning export — stories about versioning export in this arenaVersioning export | 2 | none | 0/10 | ||
Frames can behave responsively — auto layout, constraints, and grids resize designs the way real UIs flex C Canvas | designer | Vector editing — stories about vector editing in this arenaVector editing | 2 | none | 0/10 | ||
Manage design tokens or variables — colors, spacing, typography — with modes or themes applied across designs C Design systems | designer | Components design systems — stories about components design systems in this arenaComponents design systems | 2 | none | 0/10 | ||
Self-host the full design platform on my own infrastructure under an open-source license C Files | developer | Versioning export — stories about versioning export in this arenaVersioning export | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Extend the editor from a large plugin community or marketplace — icons, data fillers, accessibility checkers, and more G Plugins | designer | Plugins extensibility — stories about plugins extensibility in this arenaPlugins extensibility | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Prototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product C | designer | Prototyping — stories about prototyping in this arenaPrototyping | 1 | full | 8/10 | Cclaimed | |
The file format is open or documented, so my designs stay portable and toolable outside the vendor's editor C Files | developer | Versioning export — stories about versioning export in this arenaVersioning export | 1 | partial | 5/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 5/10 | Cclaimed | |
Built-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editor C Ai | designer | Ai design — stories about ai design in this arenaAi design | 1 | partial | 3/10 | Cclaimed | |
Published plan pricing makes seat types, tiers, and AI-feature gating clear before procurement G Pricing | product manager | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 1 | partial | 2/10 | Cclaimed |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 37 stories with headroom
What would move Spline’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
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.
Dev handoff — stories about dev handoff in this arenaInspect any layer and get measurements, styles, assets, and code snippets (CSS/iOS/Android) without an editor seat
nonemoves PA Scoreimpact 30
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.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
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.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
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.
Agenticness — how well agents can access and operate the productRun the product headlessly / in CI for automation
nonemoves agent-readyimpact 30
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.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: any documentation of credential/token scoping, permission levels, or least-privilege API key issuance for agents.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
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.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
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.
Showing the top 8 of 37 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map10 surfaces · 29 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Basics docs19 stories
- An agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them
- An agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface
- My coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Built-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editor
- Generate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually produces
- Define rules that trigger actions automatically on events
- Comment directly on designs, mention teammates, and resolve threads so review happens in the file, not in email
- My whole team can edit the same file simultaneously with live cursors and instant sync
- Do everything through the API that I can do in the UI
- The free tier supports real design work — usable editor and collaboration without a paid seat
- Prototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product
- Wire screens into clickable prototypes with triggers, transitions, and overlays — no code required
- I get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design work
Exporting your scene docs10 stories
- An agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them
- An agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface
- My coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design
- Drive the product through a documented public API
- Build against official SDKs
- Designs map to production code — component-to-code mappings or direct design-to-code output I can actually ship
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Prototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product
- The file format is open or documented, so my designs stay portable and toolable outside the vendor's editor
Interaction states events and actions docs9 stories
- An agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them
- My coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Do everything through the API that I can do in the UI
- Prototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product
- Wire screens into clickable prototypes with triggers, transitions, and overlays — no code required
Designing in 3 d docs7 stories
- Version, review, and roll back my automations
- Build reusable components with variants and per-instance overrides that stay linked to their source
- Shared libraries publish components and styles across files and projects, with controlled updates when the source changes
- Prototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product
- Wire screens into clickable prototypes with triggers, transitions, and overlays — no code required
- I get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design work
- Full version history lets me name milestones, compare, and restore any earlier state of a file
Generate docs6 stories
- An agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them
- My coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Operate the product with natural-language commands
- Do everything through the API that I can do in the UI
Pricing docs6 stories
- Version, review, and roll back my automations
- Shared libraries publish components and styles across files and projects, with controlled updates when the source changes
- Export all of my data in open formats and leave
- Published plan pricing makes seat types, tiers, and AI-feature gating clear before procurement
- The free tier supports real design work — usable editor and collaboration without a paid seat
- Full version history lets me name milestones, compare, and restore any earlier state of a file
OpenAPI spec5 stories
- An agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them
- An agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface
- Drive the product through a documented public API
- Build against official SDKs
- Do everything through the API that I can do in the UI
Spline AI docs5 stories
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Built-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editor
- Generate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually produces
- Do everything through the API that I can do in the UI
Hana a canvas for interactivity docs3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -sL https://docs.spline.design/llms.txt | head -3reproduced$ curl -sL https://docs.spline.design/llms.txt | head -3 # Spline Documentation ## Docs
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
2 of 12 testable claims verified · 0 contradicted → integrity 17/100
19 distinct capability claims found in Spline’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
2
Verified
10
Unverified
0
Contradicted
17
Undersold
Verified (4)
“A Code API lets external code trigger actions, modify object properties, and drive scene behavior programmatically”
Drive the product through a documented public APIpartialproof ↗
“A Real-time API lets you integrate external services, send/receive data, and automate responses to events”
Drive the product through a documented public APIpartialproof ↗
“An official Spline MCP Server lets MCP clients like Claude, Cursor, and Codex drive the editor directly”
“Desktop app's bundled MCP server auto-registers with Claude, Cursor, VS Code, Antigravity or ChatGPT with zero install/config”
Unverified (11)
“Real-time cloud-based multiplayer editing where several people can edit the same file at once”
My whole team can edit the same file simultaneously with live cursors and instant syncfullproof ↗
“AI agent builds and edits full 3D scenes (objects, materials, lighting, animation, interactivity) from a text description”
Generate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually producesfullproof ↗
“AI-generated textures (grass, concrete, wood, ceramic, patterns) created just by typing a prompt”
Built-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editorpartialproof ↗
“Reusable components whose instances update automatically when the main component changes”
Build reusable components with variants and per-instance overrides that stay linked to their sourcepartialproof ↗
“Self-hosted export packages the entire project, assets, and Spline runtime as a self-contained ZIP for your own hosting”
“Webhooks let a project listen for external events and automatically trigger actions or update variables in response”
“Scenes can be exported as production code: Vanilla JS, Three.js, React, Next.js, or react-three-fiber”
Designs map to production code — component-to-code mappings or direct design-to-code output I can actually shipfullproof ↗
“Version History lets you preview, track, manually save, and recover previous versions of a file”
Full version history lets me name milestones, compare, and restore any earlier state of a filepartialproof ↗
“Hana AI generates a UI screen design from a text description, which can then be hand-edited”
Generate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually producesfullproof ↗
“Most interactivity requires no code — built from a no-code system of states, events and actions”
Wire screens into clickable prototypes with triggers, transitions, and overlays — no code requiredpartialproof ↗
“Team Library feature for sharing assets/components across a team”
Shared libraries publish components and styles across files and projects, with controlled updates when the source changespartialproof ↗
Undersold (17)
An agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read themfullproof ↗
An agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surfacepartialproof ↗
My coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the designpartialproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
Operate the product with natural-language commandsfullproof ↗
Define rules that trigger actions automatically on eventsfullproof ↗
Comment directly on designs, mention teammates, and resolve threads so review happens in the file, not in emailpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Published plan pricing makes seat types, tiers, and AI-feature gating clear before procurementpartialproof ↗
The free tier supports real design work — usable editor and collaboration without a paid seatpartialproof ↗
Prototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real productfullproof ↗
I get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design workpartialproof ↗
The file format is open or documented, so my designs stay portable and toolable outside the vendor's editorpartialproof ↗
Claims outside our story set (4)
Real capability claims found in Spline’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Design and ship interactive 3D/2D experiences to web, iOS and Android without writing code”
source ↗“A native <spline-viewer> HTML web component can embed published scenes in any web builder, framework, or browser”
source ↗“A file can embed a full HTML/CSS/JS document rendered in a sandboxed iframe layered over the 3D canvas”
source ↗“Desktop app supports working across multiple files in tabs and uses installed system fonts”
source ↗
Business model
Free personal plan, then per-seat Super/Super Team tiers that unlock exports, higher limits, and AI features; custom Enterprise contracts.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
