> 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/how-to.../faq.md).

# FAQ

### New to Pletor

<details open>

<summary>What can I do with Pletor?</summary>

Two things:

* **Produce assets:** images, video, text, and audio across a wide library of models, all from one workspace.
* **Build systems:** agents that produce on repeat. Deploy them as Apps for your team, scale them with Batch, and connect them to your stack through MCP and the API.

</details>

<details>

<summary>Which models are available?</summary>

Pletor orchestrates the best models across image, video, text, and audio: Google, OpenAI, ByteDance, Kling, Flux, Recraft, ElevenLabs, and more. Pick the right one per task without managing separate accounts.

See [Models](/models/text-models.md).

</details>

<details>

<summary>How can I build good creative agents?</summary>

Start from scratch, from a template or with a little help from AI.

**The principles:**

* Start simple. One clear job per agent.
* Structure your inputs. A few well-defined inputs beat many loose ones.
* Let text models with custom instructions do the heavy lifting. Strong prompting beats complex node graphs.
* Pick the right model for the task. Validate the fit by producing a few variants.
* Split into as many steps as you need control. Each step is a checkpoint.

**The path:**

* Pick a template. Browse Templates for your use case and run one as-is to see a result fast.
* Customize in Studio. Adjust its nodes: inputs, models, brand, and logic.
* When ready, scale your production with [Apps](/automate/apps.md), [Batch](/automate/batch.md), [MCP](/automate/pletor-mcp.md) & more.

</details>

<details>

<summary>How does pricing work?</summary>

Pletor runs on a credit-led model across different [plans](/get-started/welcome.md). Each plan includes a monthly credit allowance and a set of features. You spend credits as you produce.

Visit [Billing & invoices](/how-to.../billing-and-invoices.md) for more.

</details>

### Building your creative system

<details>

<summary>How can I pick the right model for my need?</summary>

* When in doubt, start with the go-to models. They handle most jobs well.
* Browse the [model library](https://app.notion.com/p/lasqo-ai/LINK) to compare capabilities and pricing.
* Otherwise ask the AI assistant. Describe your task and it will recommend a model.

</details>

<details>

<summary>How can I personalize my agents with my brand?</summary>

Two levers:

* **Brand system nodes**: static brand elements baked into the agent. They don't appear as inputs when deployed as an app.
* **Your Brain**: set up your Brain once, then use it when building agents. Either through Brain nodes (synced with your Brain's content) or directly in chat by loading your Brain.

</details>

<details>

<summary>How can I iterate without burning credits?</summary>

* Test with cheap, fast models first. Switch to premium models once the structure works.
* Run single steps instead of the full agent while building.
* Validate prompts with one output before producing variants.
* Work at lower resolutions or shorter durations during drafts, scale up for finals.

</details>

<details>

<summary>How can I make others run my agents?</summary>

Deploy them as apps. Anyone on your team can then run them through a simple, prompt-driven interface, no Studio access needed.

See: [Apps](/automate/apps.md)

</details>

<details>

<summary>How can I integrate Pletor with external systems?</summary>

Two ways: API or MCP.

Use the API for programmatic integrations inside your own systems or through tools like n8n, Zapier, or Make. See: [API integrations](/automate/api-integrations.md)

Use MCP for conversational integrations, connecting Pletor to agents and AI assistants like Claude. See: [Pletor MCP](/automate/pletor-mcp.md)

</details>

<details>

<summary>How do I connect Pletor's MCP to Claude?</summary>

In Claude, go to Settings → Connectors and add a custom connector. Name it Pletor and use this server URL: `https://api.pletor.ai/mcp`. Once connected, Claude can run your Pletor agents directly: [Pletor MCP](/automate/pletor-mcp.md)

</details>

<details>

<summary>How do I get API access and an API key?</summary>

API access is available on paid plans. Get your key in [Settings → API](https://app.pletor.ai/?settings=api).

</details>

<details>

<summary>What's the maximum input size in Pletor?</summary>

40 MB per file.

</details>

### Collaboration

<details>

<summary>How can I work with my team on Pletor?</summary>

Collaboration happens at several layers:

* **Shared workspace.** Agents and assets in your workspace are shared, everyone builds on the same foundation.
* **Apps.** Deploy agents as apps so teammates can run them without touching Studio.
* **Brain.** One shared Brain keeps everyone's output on-brand.

</details>

<details>

<summary>Can I invite my team to Pletor?</summary>

Yes, on all paid plans. Invite teammates to your workspace and they can run your apps, or build alongside you in Studio.

</details>

<details>

<summary>Can I restrict which models my team uses?</summary>

Yes. Model restrictions are available on Studio and Enterprise plans.

</details>

<details>

<summary>How do I keep a face/character consistent across video shots, and improve lip-sync?</summary>

</details>