> For the complete documentation index, see [llms.txt](https://hengutility.gitbook.io/hengutility-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hengutility.gitbook.io/hengutility-docs/knowledge/utility-access-connection-system.md).

# Utility Access Connection System

This section explains how a utility-based connection system allows users to activate or unlock specific features on digital platforms using utility tokens.
\
It functions solely as a user-controlled tool within decentralized systems.

Key Characteristics:
\
✅ Provides access to platform features or services through authorized token-based interactions,
\
✅ Operates using decentralized verification for security and transparency,
\
✅ Does not function as a financial tool or involve payments, profits, or trading activities.

All activities are designed purely for non-financial digital access, such as activating features, viewing services, or participating in decentralized tools.

***

⚠️ Important Notice:
\
This content is intended for general informational purposes only.
\
It does not involve financial products, investment offers, or promises of return.
\
All features are for utility access within authorized platforms only.


---

# 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://hengutility.gitbook.io/hengutility-docs/knowledge/utility-access-connection-system.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.