> For the complete documentation index, see [llms.txt](https://docs.wagon.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wagon.network/products/data-network-upcoming/data-sources.md).

# Data Sources

Wagon collects operational data directly from the assets that tokenized through the protocol. These sources ensure that all insights are rooted in real-world activities.

Here are the key data sources:

* **Borrower App**\
  Borrowers input updates on delivery, usage, maintenance, and payment through the mobile or web app provided by Wagon.
* **Leasing Contracts & Invoices**\
  Data from legally binding leasing documents are recorded and linked to each financed asset.
* **GPS & Telematics**\
  Integration with fleet management tools or trackers can provide live location, mileage, and performance logs.
* **Repayment Logs & Performance**\
  On-chain repayment and rental income streams are tracked to build credit profiles and risk models.
* **Manual Verification & Field Reports**\
  Wagon operations team may conduct checks or request photo/video uploads to validate activity.

All collected data is time-stamped, validated, and securely stored — ensuring transparency, accuracy, and accountability while respecting data ownership.


---

# 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://docs.wagon.network/products/data-network-upcoming/data-sources.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.