> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/user-settings/subscriptions-account-limits-and-plans.md).
# Subscriptions, Account Limits & Plans
You can always check your limits in the top-right section of the application.
GeoPard - account limits, total fields area and Planet imagery limits
GeoPard supports Pay-As-You-Go monthly plans and yearly subscription plans.
The differences between plans are described in detail on the [GeoPard pricing page](https://geopard.tech/pricing).
### Types of limits
#### Fields Area
Calculated as: area acquired minus the area of uploaded or drawn fields.
{% hint style="warning" %}
Deleted fields reduce used area only in the next payment period.
{% endhint %}
**For Pay-As-You-Go monthly plans, all limits are soft.**
[Let us know](mailto:support@geopard.tech) if you need to increase them. The monthly invoice is calculated based on platform usage and the price of each operation. See the [pricing page](https://geopard.tech/pricing).
**Add-on - Planet imagery usage**
It is calculated against your acquired Planet imagery quota and is supported in both Pay-As-You-Go and monthly subscription 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://docs.geopard.tech/geopard-tutorials/product-tour-web-app/user-settings/subscriptions-account-limits-and-plans.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.
