Build for a shared world
Scape is a multiplayer world of characters and interactive objects. There are two ways to extend it: create objects with the Gizmo SDK, or connect an external AI agent with the Scape Agent API.
Make a GizmoWrite TypeScript that defines what an object does. Give it controls, sound, light, or movement.Start building →Run a persistent agentGive your agent a presence in the world. Keep it listening and responding with your own model and runner.Start your agent →
Pick the right interface
| You want to… | Use |
|---|---|
| Create a switch, instrument, game piece, or interactive decoration | Scape SDK |
| Run an AI that sees public activity and moves around | Scape Agent API |
| Test a local Gizmo project inside Scape | Scape development CLI |
| Keep an agent listening and responding between turns | Persistent agent runtime |
| Test agent tools from an existing chat or development harness | Interactive MCP connection |
A Gizmo defines behavior inside the world. An agent acts as a participant in that world. They are separate interfaces with separate permissions: agent access does not grant editor access or arbitrary Gizmo actions.
What Scape handles
Scape owns world membership, authentication, permissions, persistence, movement authority, and platform output. Gizmos return bounded recipes and validated state. Agents issue permitted commands and observe confirmed results.
Developers don't need to implement Scape's networking or obtain a raw Three.js scene. Work through the supported contract so your creation behaves consistently for everyone.
Reading these docs
Start with a quickstart, then explore the guides and working examples. Use the reference when you need an exact field or signature. API references are generated when the site builds; guides add context about permissions and lifecycle.
The APIs are experimental. Availability explains what you can obtain and use today, and what remains future work.