Benchy documentation
One account, four products, and an MCP server your agent can drive. These pages cover sign-on, agent setup, publishing 3D work, and the open engine underneath.
Benchy is a family of 3D creator tools built for people and agents to drive interchangeably. What you can do in the UI, an agent can do through one MCP endpoint using your credentials — and the engine that decides whether a file passes its checks is open source, so you can run it yourself.
The benchy.world wordmark returns to the model catalogue. The header's only other action takes you to sign in or, when you already have a session, to your dashboard; documentation navigation stays inside this page.
The Benchy family
Benchy is four sites sharing one account. benchy.studio holds your account and the family-wide MCP server; benchy.bio, benchy.shop, and benchy.world are separate products, each with its own database, so trouble on one never spreads to the others.
| Site | What it is |
|---|---|
| benchy.studio | Your account, Benchys, the canvas, and the MCP server at mcp.benchy.studio |
| benchy.bio | Link-in-bio maker profiles built from bento blocks |
| benchy.shop | Creator commerce — digital products sold through Stripe Connect |
| benchy.world | Versioned 3D asset hosting, discovery, packages, rights, and workflow evidence — where you are now |
One account everywhere
One Benchy account signs you in to studio, bio, shop, and world. Create it at benchy.studio, then sign in from any site in the family — there is nothing to link and no second password. Getting started covers accounts and single sign-on.
Built for agents
Benchy treats agents as first-class users. One MCP endpoint exposes scoped tools across the family — bio profiles, the Studio canvas, world models, shop commerce, documents, agent knowledge, and Box packets — with personal access tokens, OAuth for hosted connectors, and an audit log for every call. The set of tools a caller sees reflects that caller's account access, credential scope, and the safety gates the server has in effect. The hosted agent at benchy.studio runs on that same permissioned surface with your credentials; there is no privileged internal API.
Open at the foundation
The layer of Benchy that identifies a file, runs bounded checks, and records a policy decision — benchy-mesh, the Rust mesh-validation engine — is open source, dual-licensed MIT OR Apache-2.0, and runnable by anyone. The Open source section documents the engine, its grading harness, and the edge pipeline architecture around it.
Where to go next
The blog covers the thinking behind the architecture: Building Benchy.
Use ← and → to move between pages.