> 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/faq/do-you-have-a-partner-friendly-plan.md).

# Do you have a Partner-friendly plan?

If you have a store that will never see customer traffic, then we can help out with this. :) Mechanic doesn't have separate plans, but we do grant super-extended trial periods for development stores. Write in to <team@usemechanic.com>, making sure to include your store name, and we'll help you out.

Learn more about our approach to this here: [Platform / Policies / Plans / Development stores](/platform/policies/plans.md#development-stores).

{% hint style="info" %}
Did you know we have [a Slack workspace you can join](/resources/slack.md)? It's true! This is the right place to ask implementation questions, and to compare notes with other problem-solvers. Come join us!
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.mechanic.dev/faq/do-you-have-a-partner-friendly-plan.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.