> For the complete documentation index, see [llms.txt](https://docs.marketingtool.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketingtool.pro/product/faq.md).

# FAQ

Frequently asked questions

<details>

<summary>Are all tools available on the free plan?</summary>

Yes. Every tool is open on every plan — plans only set your monthly generations. See [Plans & credits](/getting-started/plans-and-credits.md).

</details>

<details>

<summary>What's a "generation"?</summary>

One tool run. Starter includes 200/month, Pro 500, Growth 1,500+ — and you can top up **100 extra generations for $3** anytime.

</details>

<details>

<summary>Is the credit balance I see real?</summary>

Yes. The balance shown in the app is your live, actual balance.

</details>

<details>

<summary>Do the mobile apps have fewer features than the web?</summary>

No — both apps mirror the full tool catalog with the same interface. The web app adds desktop-sized result pages, **Download All**, and the Analytics / Campaigns / Reports / Command Centre workspaces.

</details>

<details>

<summary>Which AI does MarketingTool.Pro use?</summary>

MarketingTool.Pro runs its own AI pipeline tuned for marketing work, combining multiple state-of-the-art models with automatic failover, so results stay fast and reliable.

</details>

<details>

<summary>Can I use my results commercially?</summary>

Yes — everything you generate with your account is yours to use.

</details>

<details>

<summary>Can I switch between phone and desktop mid-task?</summary>

Yes. History is account-wide and live — a run made on your phone is waiting in the web app, at full desktop size.

</details>

<details>

<summary>How do I get support?</summary>

Ask MarketBot in the app, or email <Help@marketingtool.pro>.

</details>


---

# 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.marketingtool.pro/product/faq.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.