> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-graphql-api/tracking/guides.md).

# Guides

{% hint style="warning" %}
**Navixy GraphQL API is a work in progress.** This documentation is published for preview purposes only and doesn't reflect a stable release. Structure, field names, and behaviors are subject to change.
{% endhint %}

This section contains step-by-step guides for the basic scenarios of using Tracking, a product served by Navixy GraphQL API. Each guide builds one view that a fleet application needs, from the first query to the stream or the request that keeps it complete.

### Guides in this section

* [Building a live fleet map](/docs/navixy-graphql-api/tracking/guides/building-a-live-fleet-map.md): where every asset is, whether it moves and reports, and what its sensors say, kept current with a state stream
* [Reading a vehicle trip history](/docs/navixy-graphql-api/tracking/guides/reading-a-vehicle-trip-history.md): request a device and period, receive trips and stops with totals, complete a partial result, and load the route of each trip


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/navixy-graphql-api/tracking/guides.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.