> 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/wagon-products.md).

# Wagon Products

Wagon Network offers three core components that power asset tokenization and data for real-world assets:

***

#### 1. Asset Tokenization

Invest in tokenized supply chain assets like trucks and equipment. Earn yield from rental activity, tracked and paid on-chain.

{% content-ref url="/pages/PO4nrcnwbA4kQ4uLi258" %}
[Wagon Asset Tokenization](/products/wagon-asset-tokenization.md)
{% endcontent-ref %}

***

#### 2. $WAG Token & Staking

Stake **$WAG** to earn rewards, boost your returns, and participate in the protocol’s future governance.

{% content-ref url="/pages/rNLcXibHkKOOl2xHLmJL" %}
[$WAG Token & Staking](/products/usdwag-token-and-staking.md)
{% endcontent-ref %}

{% content-ref url="/pages/Wl3oH53PM7yC8owqvBMA" %}
[Staking](/products/usdwag-token-and-staking/staking.md)
{% endcontent-ref %}

***

#### 3. Wagon Data Layer *(Upcoming)*

Operational data from tokenizard assets is stored on-chain — powering analytics, credit scoring, and enterprise integrations.

{% content-ref url="/pages/jxRFWuROt7AaSl8VRRfS" %}
[Data Network (Upcoming)](/products/data-network-upcoming.md)
{% endcontent-ref %}

***

These products work together to bring transparency, utility, and real-world value into the blockchain ecosystem.


---

# 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.wagon.network/products/wagon-products.md?ask=<question>&goal=<user_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.