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

# Plans

Four plans, from free to fully custom, and what each unlocks.

Four plans. Start free, upgrade when the loop earns it.

* **Free** is for seeing it work: install the pixel, see who visits by name, build your first audience. Single-player; it stops when the credits run out.
* **Pro** adds room to run: more credits, a small team, and the loop working your goal.
* **Team** is the full always-on system across a growing team and multiple workspaces, with overage available so the loop never stalls mid-month.
* **Enterprise** is custom: your scale, your deployment, your terms. [Book a demo](https://www.icustomer.ai/contact).

Credits are the single unit of usage, drawn as the system works and shared across the owner's workspaces. The mechanics, categories, overage, and plan changes live in [Billing](/settings/billing.md).

{% hint style="info" %}
Prices, credit allotments, and seat counts live on [icustomer.ai/pricing](https://www.icustomer.ai/pricing).
{% endhint %}


---

# 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.aloop.icustomer.ai/getting-started/plans.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.