> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-developer-tools/protocol/utility-features.md).

# Utility Features

The æternity blockchain offers essential utility services that enhance user experience and enable seamless integration with external systems. The æternity Naming System (AENS) allows users to replace complex 256-bit addresses with human-readable names, similar to how DNS works for the internet, making blockchain interactions more intuitive and user-friendly. Serialization Formats standardize how data is encoded, decoded, and transmitted across the network, ensuring consistent communication between different nodes and services. These utility services form the backbone of æternity's user-centric approach to blockchain technology, making it easier for both developers and end-users to interact with the ecosystem. The sections that follow provide comprehensive guides on how to implement and utilize these essential network utilities.


---

# 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.aeternity.com/aeternity-developer-tools/protocol/utility-features.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.
