> For the complete documentation index, see [llms.txt](https://docs.visiongame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visiongame.io/visionnexus-depin/visionnexus-license-node.md).

# VisionNexus License Node

The VisionNexus License Node is your gateway into VisionGame’s decentralized physical infrastructure (depin) network. Designed to be accessible and affordable, VisionNexus License Nodes provide node holders with the ability to contribute storage, computational power, and other resources, supporting both VisionGame’s products and additional services in need.

One of the key distinctions of the VisionNexus License Node is its affordability compared to traditional nodes, allowing more participants to join and benefit from the network. VisionNode holders receive even more: as part of their core perks, they gain access to one VisionNexus License Node for free, granting them seamless entry into our depin ecosystem.

With VisionNexus License Nodes, VisionGame is expanding its infrastructure while keeping community empowerment at the forefront, enabling a wider audience to participate in and benefit from our decentralized 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 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.visiongame.io/visionnexus-depin/visionnexus-license-node.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.