> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/transparent-and-user-friendly-pricing.md).
# Transparent and User-Friendly Pricing
* Simplified Pricing Model: Unlike other tools that charge per template (like Workato), per action (Zapier), or items in sync (Unito), Getint's pricing is based on the number of instances integrated.
* Unlimited Integration: Integrate as many projects and tasks as you need without worrying about additional costs. We encourage extensive usage as it reflects the tool’s value and necessity.
* Predictable Costs: With clear pricing, enjoy peace of mind and predictable billing, making it easier for accounting and budget planning.
* No Usage Penalties: Our pricing model is designed to encourage rather than limit your usage. The more you use Getint, the more value it brings to your team’s efficiency.
In conclusion, Getint not only delivers a wide array of features for effective data synchronization but also ensures a transparent and straightforward pricing model. This approach allows your teams to maximize efficiency without the worry of unexpected costs or limitations.
---
# 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.getint.io/transparent-and-user-friendly-pricing.md?ask=&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.
