> For the complete documentation index, see [llms.txt](https://docs.integry.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.integry.ai/users-and-billing/how-is-usage-measured.md). # How is usage measured? Integry has two usage models that you can pick from when you sign up: User-based pricing or Run-Based pricing. Here are the details for both ### **User-based pricing** Pay per user of your app that sets up an integration * A User can be an end-use, account or business in your app. The Integrations are visible to them. * Access to all apps * Setup any number of integrations * Limited by your account’s throughput * Volume discounts available * Good for: when you have lots of integration usage per user ### **Run-based pricing** Pay whenever an integration Runs * A Run can pull in any amount of data * Access to all apps * Setup any number of integrations * Fair usage applies * Volume discounts available * Good for: when you have sporadic usage per account Depending upon how your SaaS app is priced and what your usage pattern looks like, one or the other model will make sense. Please reach out to your success manager if you need help in deciding. You can also [setup a call with sales](https://integry.ai/talk) to discuss your options. --- # 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.integry.ai/users-and-billing/how-is-usage-measured.md?ask=&goal= ``` `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.