> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/platform/policies/plans.md).

# Plans

**Mechanic does not have different plans.** The following details apply to every Mechanic account:

* Each account in good standing may install an unlimited number of [tasks](/core/tasks.md), may receive an unlimited number of [events](/core/events.md), and may process an unlimited number of [runs](/core/runs.md).
* Each account has a limited-term trial period, during which no billing agreement is required.
  * When the trial period expires, Mechanic will suspend the account, and will stop processing incoming events for that account.
  * Shopify stores that will only be used for development and testing, which will never see production customer traffic, are invited to write to <team@usemechanic.com> to request a super-extended trial period.
* Every account qualifies for our [pay-what-feels-good pricing policy](/platform/policies/pricing.md), in which our system offers a suggested price based on Shopify plan type, inviting the user to contact <team@usemechanic.com> to talk about what price feels good to them.
  * Mechanic exclusively uses monthly billing.
* Every account is subject to our [data policy](/platform/policies/data.md).

## Development stores

Mechanic is Partner-friendly! If you have a Mechanic account used exclusively for development or testing, receiving no customer traffic, send the core team an email at <team@usemechanic.com>. We can usually help out by granting a super-extended trial period. :)


---

# 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://learn.mechanic.dev/platform/policies/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.
