Benchy documentation
One account, four products, and an MCP server your agent can drive. Start here for the map of the Benchy family and where everything lives.
Benchy is a family of 3D creator tools built around one idea: the next generation of asset platforms will be operated by agents and trusted because their foundations are open. These docs cover the whole surface — your account, your shop, your models, the open-source validation engine underneath, and the skills that teach any agent to run it all for you.
The Benchy family
The family is a hub and spokes. The hub owns identity and the family-wide MCP server; each spoke is its own product with its own database and its own blast radius.
| Site | What it is |
|---|---|
| benchy.studio | The hub — 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
You sign up once. The hub mints short-lived, cryptographically signed tokens that every spoke verifies independently — no shared database, nothing long-lived crossing a boundary. Your login on benchy.world is the same login on studio, bio, and shop. Getting started walks through accounts and single sign-on.
Built for agents
Benchy treats agents as first-class users. One MCP endpoint exposes scoped tools across the family — profiles, shop, models, canvas — with personal access tokens, OAuth for hosted connectors, and an audit log for every call. The exact tool set reflects the caller's access, credential scope, and deployment safety gates. Our own hosted agent uses 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
Prefer prose? The blog covers the thinking behind the architecture — Building Benchy.
Use ← and → to move between pages.