Overview

Generate stylized 3D game scenes from text — from your own code, your CI, or the coding agent you already use.

Scenebrew turns a written brief into a playable 3D scene. The pipeline has four steps, and every one of them is reachable from outside the app as a scene step:

generate_scene_sdd — an AI author expands your brief into a Scene Design Document.
generate_scene_peg — an AI builder turns the design into a Player Experience Graph.
generate_scene_blueprint — a procedural step turns the graph into a blueprint and a layout preview.
generate_scene_model — a procedural step turns the blueprint into a GLB you can drop into an engine.

Only the two AI steps cost credits. Blueprint and model are free, so a client that brings its own SDD and PEG pays nothing.

Around the pipeline sit the things a real integration needs: projects to own scenes, files you upload once and reference by id, sessions — conversations with Scenebrew's own agent — and the library of themes, designs, recipes and assets a scene draws on. Anything slow runs as an operation you can wait on, poll or cancel.

Three ways in

REST API

https://api.scenebrew.com/v1 — JSON over HTTPS, API keys as Bearer tokens, problem+json errors. Everything the app can do with a scene, from any language.

MCP server

https://mcp.scenebrew.com/v1/mcp — the same operations as tools for Claude Code, Codex, Cursor, Zed and any other MCP host. One name per action on both surfaces.

OpenAPI contract

The API publishes its own OpenAPI 3.2 document. This reference is rendered from it, and so can your client.

Start here

Getting started

Create a key and walk through the read endpoints with curl.

Generate a scene

Drive the four pipeline steps end to end and download the GLB.

Operations

Wait, poll and cancel — the one async model behind steps, turns and generations.

API reference

Every operation, with schemas and an in-browser playground.

Stability

The API is versioned by path: everything documented here lives under /v1. Compatible additions — new fields, new operations — ship without notice beyond the changelog. A field or operation that has to go is marked deprecated first and removed only after a published sunset date. A breaking change would ship as a new path generation, side by side with /v1.

The contract version is the info.version the API reports at /openapi.json — 0.9.1 as of September 2026. The contract is pre-1.0 while Scenebrew is a development preview: there is no major, and a change that breaks callers bumps the minor and says so in the changelog, which also has the migrations.

For agents

Every page is available as Markdown — append .md to its URL (/getting-started.md), or use the copy button at the top of each page; /llms.txt indexes the site and /llms-full.txt is the whole thing in one file. Reference pages render the operation straight from the contract.