> For the complete documentation index, see [llms.txt](https://help.pagefly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pagefly.io/getting-started/pricing-and-billing.md).

# Pricing and billing

### About PageFly Pricing And Billing

It is obviously necessary for you to know all about the PageFly pricing & billing policies. The Pricing & billing section is full of information regarding this topic with related articles to all charging scenarios that may occur during PageFly use.

This section will help you to understand more about the amount you have been charged and why. You’ll also learn about the PageFly refund policy.

This section also has articles to fill you in on the details of downgrading your plan and canceling your subscription. Have a look at the articles below to learn more.

You can check our tutorial on getting started with PageFly below

{% embed url="<https://youtu.be/Z1J6lqVlGt4>" %}

### Related Resources

* [PageFly’s Terms Of Service](https://pagefly.io/pages/terms-of-service)
* [2024 Shopify Pricing Plans Demystified: Your Ultimate Guide To Calculating Costs](https://pagefly.io/blogs/shopify/shopify-pricing-plans)


---

# 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://help.pagefly.io/getting-started/pricing-and-billing.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.