> For the complete documentation index, see [llms.txt](https://docs.m-xr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md). # Credits & billing Marso Studio runs on **credits**. Every generation step spends a set number, and your balance is shown at the top of the screen at all times. Costs scale with the work involved — generating an image is cheap, generating and texturing a 3D object costs more, and a scene costs the sum of its objects. The one choice that moves the total most is **which 3D generator you use**. The cheapest and the most expensive are four times apart, and that gap multiplies across every object in a scene. ## What each step costs | What you do | Node | Credits | | ---------------------------------- | ------------------------- | ---------------------- | | Apply PBR materials | Generate PBR Textures | **30** | | Image → 3D model | Generate 3D Model | **30–120** — see below | | Generate a scene image | Scene Generation | **10** | | Break a scene into objects | Detect Objects | **20** | | Reference images for scene objects | Generate Reference Images | **10** per object | | Generate an image | Image Generation | **10** | | Edit an image | Image Edit | **10** | | Generate a multi-view image set | Multiview | **2** | | Upload an image | Image Upload | Free | | Upload a 3D model | 3D Model Upload | Free | | Mesh compression | — | Free, automatic | See the [Nodes reference](/marso-studio/reference/nodes-reference.md) for what each step does. ## What the 3D generators cost **Generate 3D Model** lets you pick which reconstruction model runs, and they aren't priced the same: | Generator | Single image | Custom face count | Multi-view input | | --------------------------- | ------------ | --------------------- | ---------------- | | **Tripo H3.1** | **30** | 30 — no extra charge | Not supported | | **Hunyuan 3.1** *(default)* | **40** | 55 *(+15)* | **60** | | **Meshy 6** | **80** | 80 — no extra charge | Not supported | | **Meshy 7** | **120** | 120 — no extra charge | Not supported | **Tripo H3.1 is the cheapest**, and cheaper than the default. **Meshy 7 is four times its price.** Switching generator re-runs the generation, charged at that generator's rate. > **Custom face count is only charged on Hunyuan 3.1.** Setting a target polycount adds **15 credits** to Hunyuan's base, so a Hunyuan generation with a custom face count is **55 credits** — and on Hunyuan it's single-image only. On Tripo H3.1, Meshy 6 and Meshy 7 a custom face count is included in the base price. Only **Hunyuan 3.1** accepts multi-view input, so the **Multiview** node (2 credits) feeds a Hunyuan generation. ## Budgeting a run Plan per object, not per pipeline — and settle on a generator first, because it sets the per-object cost. **One object, generated from scratch and textured:** | Step | Tripo H3.1 | Hunyuan 3.1 *(default)* | Meshy 6 | Meshy 7 | | --------------------- | ---------- | ----------------------- | ------- | ------- | | Image Generation | 10 | 10 | 10 | 10 | | Generate 3D Model | 30 | 40 | 80 | 120 | | Generate PBR Textures | 30 | 30 | 30 | 30 | | **Per object** | **70** | **80** | **120** | **160** | **One object you already have — 30 credits**, whichever generator is selected. Upload it and run Generate PBR Textures; uploading is free and no reconstruction runs. **A scene — 30 credits up front, plus the per-object cost above.** The scene image and the detection are charged once; then every object you keep runs its own reference image, 3D model and PBR: | Stage | Charged | Credits | | --------------------- | ---------- | ------------------------ | | Scene Generation | once | 10 | | Detect Objects | once | 20 | | Reference images | per object | 10 | | Generate 3D Model | per object | **30–120, by generator** | | Generate PBR Textures | per object | 30 | So a scene is **30 + (per-object cost × objects)**: | Objects kept | Tripo H3.1 | Hunyuan 3.1 | Meshy 6 | Meshy 7 | | ------------ | ---------- | ----------- | --------- | --------- | | 10 | **730** | **830** | **1,230** | **1,630** | | 20 | **1,430** | **1,630** | **2,430** | **3,230** | **Check the generator before you run a large scene.** The same twenty-object scene is 1,430 credits on Tripo H3.1 and 3,230 on Meshy 7 — more than double, for an identical selection. Running detection again, if the first decomposition isn't right, is another 20. How many objects you keep after detection is the other place you control the cost — see [Detecting & selecting objects](/marso-studio/scenes/detecting-and-selecting-objects.md). ## Free credits You get a starting balance of free credits when you sign up, and a further allowance on any day you open Marso Studio. The daily allowance **doesn't roll over** — a day you don't log in isn't banked. Your current balance is always shown at the top of the screen. ## Buying credits 1. Click **Credits** at the top of the screen. 2. Choose a pack: | Pack | Price | Roughly | | ----------------- | ----- | ----------------------------------------------------------------------------- | | **2,000 credits** | $20 | A 24-object scene on the default generator — 12 objects on the most expensive | | **5,000 credits** | $50 | Two to three scenes of that size | What a pack actually gets you depends on the generator, so read those as default-generator figures. Purchased credits **don't expire**. ## Checking your balance and usage * Your credit balance is shown at the **top of the UI at all times**. * Node inputs show what the next step will cost before you run it. * For a full breakdown, open your **account → Usage & billing**, where you can review both your balance and your usage. > Scene generation is the most expensive thing you can run, because it multiplies across every object you keep. Check your balance, your selected object count **and your 3D generator** before you start a large scene — see [Working with scene results](/marso-studio/scenes/working-with-scene-results.md) if a run stops partway. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.