> 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/aeternity-naming-system-aens.md).
# æternity Naming System (AENS)
The æternity Naming System (AENS) provides human-readable names for blockchain entities like accounts, oracles, and contracts, making the system more user-friendly than working with raw cryptographic addresses. AENS implements an auction-based registration system for shorter, more desirable names, while allowing instant registration for longer names, with all names having the .chain extension in the current implementation.
The [AENS documentation](/developer-documentation/protocol/aens.md) provides comprehensive coverage of the naming system's technical specifications, including name registration mechanisms, auction procedures, protocol fees, and namespace governance. It details the commitment scheme that prevents front-running, explains name management operations (claiming, updating, transferring, revoking), and outlines important protocol upgrades like Lima and Ceres that introduced key features such as auctions and optional pre-claims. The documentation also discusses potential future extensions like decentralized name exchange and interoperability with other naming systems.
---
# 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/aeternity-naming-system-aens.md?ask=&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.
