> 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/nor/produktomvisning-nettapp/brukerinnstillinger/abonnementer-kontogrensene-og-planer.md).
# Abonnementer, kontogrensene og planer
Du kan alltid sjekke grensene dine øverst til høyre i appen.
GeoPard - kontogrenseverdier, total feltareal og grenser for Planet-bilder
GeoPard støtter månedlige Pay-As-You-Go-abonnementer og årlige abonnementsplaner.
Forskjellene mellom planene er beskrevet i detalj på [GeoPards prisside](https://geopard.tech/pricing).
### Typer grenser
#### Feltareal
Beregnes som: anskaffet areal minus arealet av opplastede eller tegnede felt.
{% hint style="warning" %}
Slettede felt reduserer brukt areal først i neste betalingsperiode.
{% endhint %}
**For månedlige Pay-As-You-Go-abonnementer er alle grenser myke.**
[Gi oss beskjed](mailto:support@geopard.tech) hvis du trenger å øke dem. Den månedlige fakturaen beregnes basert på plattformbruk og prisen for hver operasjon. Se [prissiden](https://geopard.tech/pricing).
**Tillegg - bruk av Planet-bilder**
Det beregnes mot din tildelte kvote for Planet-bilder og støttes i både Pay-As-You-Go- og månedlige abonnementsplaner.
---
# 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/nor/produktomvisning-nettapp/brukerinnstillinger/abonnementer-kontogrensene-og-planer.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.
