> 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/api-dokumentasjon/oversikt-over-geopard-api.md).
# Oversikt over GeoPard API
Siste oppdatering: 10. juli 2023
GeoPard er en presisjonslandbruksplattform med alle funksjonene tilgjengelige via API
GeoPard API-et tilbyr både GraphQL- og REST-endepunkter for sømløs interaksjon. Som både et passivt og aktivt grensesnitt lar det andre apper be programmatisk om opprettelse av analytiske avledninger og motta oppdateringer knyttet til kompleks databehandling.
Gjennom GeoPard API-et er alle rådatasett – inkludert innhøsting, maskiner, jordprøver og skannere, satellittbilder og topografi – samt analytiske avledninger som forvaltningssoner, likningskart, anbefalinger og rasterflater, lett tilgjengelige rett ut av boksen.
GeoPard API-et støtter ulike visningsalternativer for geospatiale data, og håndterer både Raster (`jpg`, `png`, `geotiff`) og Vektor (`shp`, `geojson`, `isoxml`)-formater. For en fullstendig oversikt over API-et, se vårt [blogginnlegg](https://geopard.tech/blog/upkdhsnyk1-precision-agriculture-api/).
---
# 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/api-dokumentasjon/oversikt-over-geopard-api.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.
