> For the complete documentation index, see [llms.txt](https://docs.pletor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pletor.ai/get-started/welcome.md).

# Welcome to Pletor

Pletor is the creative infrastructure for marketing teams. 

Orchestrate the best AI models, your brand context, and your performance data into production\
pipelines. Then deploy them as apps, run them at scale, or call them from your own tools.

{% embed url="<https://www.youtube.com/watch?t=8s&v=axNYD164p6s>" %}

### What you can do with Pletor

* **Produce on brand, at volume** — product imagery, static ads, UGC, video. From a single brief to every format a campaign needs.
* **Orchestrate the best models in one pipeline** — chain image, video, and text models on one canvas instead of stitching tools by hand.
* **Encode your brand, reuse it everywhere** — brand rules, references, and performance data live in one place and shape every run.
* **Deploy anywhere** — ship an agent as an app for your team, or call it from your own tools via MCP and API.

### Your path with Pletor

Four steps, from first agent to production:

1. **Understand** — how agents, nodes, and credits fit together. → [Key Concepts](/get-started/key-concepts.md)
2. **Build** — start from a [Template](/build-agents/templates.md), then [shape your own](/build-agents/custom-agents.md) in Studio.
3. **Deploy** — turn an agent into [an app](/automate/apps.md) your whole team runs.
4. **Automate** — run at volume and make agents callable from your own tools. → [MCP](/automate/pletor-mcp.md) · [API](/automate/api-integrations.md)

### Who Pletor is for

* Marketing & creative teams producing visual content at volume
* Agencies standardizing delivery across clients
* Teams that want brand and performance context encoded once, reused everywhere


---

# 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.pletor.ai/get-started/welcome.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.