> 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/api-access.md).

# API access

Marso Studio exposes an API so you can call its generation capabilities from your own tools. Endpoints are available to authenticated users — you authenticate with an **API key** that you create in the app.

### Creating an API key

1. Log in to Marso Studio.
2. Click **API** at the top of the page (near Credits).
3. Give your key a **name** and click **Create key**.
4. **Copy the key straight away and store it somewhere safe — it is shown only once.**

> **Keep your key secret.** Treat it like a password: never commit it to source control, share it, or expose it in client-side code. If a key is ever exposed, revoke it immediately.

### Managing keys

* **Revoke** a key to stop it working immediately.
* **Delete** keys you no longer need.

You can create multiple keys — for example, one per integration — and revoke them independently.

Once authenticated, the available endpoints can be accessed from within Marso Studio.


---

# 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/api/api-access.md?ask=<question>&goal=<endgoal>
```

`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.