SDKs and codegen

The contract

GET https://api.scenebrew.com/openapi.json is the OpenAPI 3.2 document the API is built from — the same file this reference is rendered from. It needs no authentication.

curl -s https://api.scenebrew.com/openapi.json | jq '.info'

Generate a client with the tool of your ecosystem (openapi-generator, openapi-typescript, datamodel-codegen, NSwag, …). Things worth knowing when you do:

• Every error response is application/problem+json; the default response of each operation is the problem document.
• size_bytes is declared int64; pick a client type that does not truncate.
• Operation ids are stable (list_projects, run_scene_step, get_operation, create_session, …), match the page names in this reference, and are the MCP tool names too.
• The four calls that start work answer 202 or 200 depending on Prefer: wait; both carry the same Operation schema, so model the response as one type.
• Pin the contract version you generated from (info.version) and diff on upgrade; the changelog lists what each version added. Pre-1.0 the minor carries breaks as well as additions, so read the entry before moving: 0.8.0 renamed every write operation, and a client generated from 0.7.0 or earlier needs regenerating, not patching.

Official SDKs

Language SDKs (Python, C# for Unity) are generated from this contract and are being regenerated for 0.9.1; they will be announced in the changelog when they are publicly installable. Until then the contract above and the MCP server are the supported integration surfaces.