> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pulze.io/llms.txt
> Use this file to discover all available pages before exploring further.

# API Reference

> Every published Scene Manager 3 endpoint, with a console for trying each one against Scene Manager on your computer.

> [!WARNING]
>
> Scene Manager 3 is in beta. Endpoints may change before release.

The Python SDK and the MCP tools are generated from the same definitions, so each operation has the same name in all of them. For what all endpoints have in common, see the [REST API](https://docs.pulze.io/scene-manager-3/developers/rest-api.md) guide.

## Sections

| Section | What it covers |
| - | - |
| Service | Whether Scene Manager is running and connected to 3ds Max |
| Setups | Creating, changing and activating setups, and their values |
| Folders | Folders of setups. A folder's values apply to its setups |
| Modules | Modules and the properties in them |
| Rendering | Starting, following and stopping batch renders |
| Variations | Rendering every combination of a set of options |
| Comments | Comments pinned on shots, for people and agents |
| Shots | Viewport and frame buffer captures for comments |
| Scene | The open scene: objects, materials, properties, selection, scripts |
| Document | Scene Manager's data in the scene, and 2.x import |
| Settings | Your settings on this computer |
| HDRI library | HDRI maps in your library folders and in the scene |

## Using the console

The console sends requests to `http://127.0.0.1:45710/api/v1`, the Scene Manager on the computer you are reading this on. There is nothing to sign in with.

> [!WARNING]
>
> These are real requests to the scene open in 3ds Max: `DELETE /setups/{id}` deletes a setup and `POST /render` starts a batch render. Check what an endpoint does before you press **Send** on anything other than a `GET`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.