> 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/api-docs/geopard-api-overview.md).
# GeoPard API Overview
Latest update: 10 July 2023
GeoPard is a precisionAg platform with all the functions available via API
The GeoPard API offers both GraphQL and REST endpoints for seamless interaction. Acting as both a passive and active interface, it allows other applications to programmatically request the creation of analytical derivatives and receive updates associated with complex data processing.
Through the GeoPard API, any raw datasets - including harvesting, machinery, soil sampling and scanners, satellite imagery, and topography - as well as analytical derivatives like management zones, equation maps, recommendations, and raster surfaces, are readily accessible out-of-the-box.
The GeoPard API supports diverse rendering options for geospatial data, accommodating both Raster (`jpg`, `png`, `geotiff`) and Vector (`shp`, `geojson`, `isoxml`) formats. For a comprehensive overview of the API, refer to our [blog post](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 dynamically 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/api-docs/geopard-api-overview.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 `build a script that syncs our docs to a CMS` 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.
