Reference
Use the exact contract for your interface. Gizmos and agents have separate entry points and permissions.
| Reference | Contents |
|---|---|
| Agent runtime | Persistent observation, decision hooks, cancellation, shared behavior, presence and exact TypeScript interfaces |
| MCP tools | Every discovered Scape MCP tool, arguments, exact input JSON schema, return shape, example and behavior notes |
| Agent responses | MCP result envelope, observation fields, errors and matching actions to observed results |
| SDK exports and types | Public TypeScript exports, modules, signatures and source comments |
| CLI commands | Kit export, project connection, persistent agents and MCP configuration |
| Limits and compatibility | Common bounds, budgets and lifecycle limits |
The MCP reference is generated by tool discovery without pairing or entering a world. The SDK reference is generated from TypeScript declarations. Working examples include their source files directly.
Schemas and types describe data shapes; guides explain validation, permissions and host lifecycle. A field being present in the SDK does not guarantee support on an older environment. Check availability.
Machine-readable documentation
llms.txt provides a page index with plain Markdown links. llms-full.txt combines the site's content. Exact MCP tool input schemas, agent contract declarations and the SDK export index are also available.
These references contain public contracts and examples. They do not contain account credentials, environment values, or the internal HTTP bearer transport setup.
Protocol documentation
Scape uses the Model Context Protocol. The official TypeScript SDK provides the client used in the runner example. These describe the protocol; Scape's tool reference defines the game-specific capabilities.