> 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-api/getting-started/introduction.md).

# Introduction

The API turns one source file into a set of PBR texture maps. You upload a 3D mesh or an image. You submit that file for generation. You then poll the run until it finishes. Each finished run gives you presigned download URLs.

#### Server

{% tabs %}
{% tab title="Production" %}
**Base URL** `https://api.marso.app/api/public/v1/`
{% endtab %}
{% endtabs %}

#### Credits

A submission reserves credits. The API refunds the credits for each item that fails. You pay only for successful results. Read your balance with `GET /account/credits`. Read the price of each action with `GET /pricing`.

#### Rate limits

Each API key has a rate limit. The default limit is 300 requests per minute. Every response has `X-RateLimit-*` headers. A `429` response also has a `Retry-After` header. This header gives the wait time in seconds.

#### Errors

Every error uses the same envelope. The `error.code` field is for programs. The `error.message` field is for people.

```json
{
  "error": {
    "code": "ASSET_NOT_FOUND",
    "message": "The asset does not exist."
  }
}
```

Any request can return these errors:

| Status | Meaning                                            |
| ------ | -------------------------------------------------- |
| `400`  | The request is not valid. Check the body.          |
| `401`  | You sent no key, or the key is invalid or revoked. |
| `403`  | Your plan does not include this feature.           |
| `404`  | The resource does not exist.                       |
| `429`  | You sent too many requests. Wait, then retry.      |
| `500`  | The server had an error.                           |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.m-xr.com/marso-studio-api/getting-started/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.