Getting started with Benchy
Create one Benchy account, understand the family of products, and see how hub single sign-on carries your identity across every site.
Create your account
Sign up on any family site — benchy.world, benchy.studio, benchy.bio, or benchy.shop. The account is created once, at the hub, and works everywhere. There is nothing to link afterwards: logging in on one site is logging in on all of them.
Your hub profile at benchy.studio is also where account-wide things live: your plan, your Benchys balance, and the Profile → API keys page where you mint personal access tokens for agents and scripts.
The products
| Product | Use it to | Role in the family |
|---|---|---|
| benchy.studio | Manage your account, credits, and the canvas; talk to the Benchy agent | The hub — identity, tokens, and the MCP server |
| benchy.bio | Build a link-in-bio maker profile from bento blocks | Spoke |
| benchy.shop | Sell digital products with Stripe Connect payouts | Spoke |
| benchy.world | Host, release, discover, acquire, and share 3D assets and model packages | Spoke |
Each spoke runs its own deployment with its own database. What ties them together is identity: the hub is the only place accounts exist, and every spoke trusts the hub's signatures — never each other's databases.
How sign-on works
Hub single sign-on is deliberately short-lived. When you (or an agent acting for you) touch a spoke, the hub mints an RS256-signed JWT that lives for 120 seconds. The spoke verifies it against the hub's published JWKS keys and then acts on its own data. Nothing long-lived ever crosses a site boundary, and a compromised spoke cannot mint credentials for another.
The token carries a few claims that gate what you can do:
sites— which spokes your account is active onshopBuyer— set for any non-blocked member, enough to buy and download on benchy.shop without being a sellerplan— your family planmcpScope— for agent calls, whether the credential is read-only or full access
Site access
Access to each spoke is tracked per account as active, waitlist, or blocked. Most accounts are active everywhere from day one. If a tool or page tells you you're not authorized on a site, visit /request-access?site=<spoke> on the hub — agents can't grant themselves site access, and neither can a spoke.
Next steps
- Connect your agent — point Claude Code, Cursor, or any MCP client at your account.
- Publish a 3D asset — upload files, create an exact package, and describe its intended workflows.
- Open your shop — onboard with Stripe Connect and list a product.
Use ← and → to move between pages.