> For the complete documentation index, see [llms.txt](https://docs.thehemera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thehemera.com/welcome/account-centric-indexing-protocol/the-advantages-of-account-centric-indexing.md).

# The advantages of Account-Centric Indexing

Account-Centric Indexing is a novel indexing protocol tackling account-level semantic data computation and retrieval. Its User-Defined Function (UDF) design allows anyone to express semantic values through a simple functional interface.

Using Account-Centric Indexing, developers can access account state changes across smart contracts and blockchains in real-time. Developers can also configure to easily index entire blockchains, or designate the wallets-of-interests and index their transactions across all EVM chains. 

Unlike traditional 'contract-centric' indexing found in Subgraphs which mainly addresses in-Dapp data retrieval, Account-Centric Indexing focuses on resolving account profiles across Dapps and chains, and thus tackles the following needs directly:

1. Configurable indexing on accounts of interests
2. Multi-chain data coverage
3. Covers use-level specific use cases

Thus account-centric indexing provides the following main advantages.:

1. Real-time access to the account-level states and history
2. Full account-level states and history coverage, including all smart contracts & chains the account has footprints on.
3. Horizontally scalable

####


---

# 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.thehemera.com/welcome/account-centric-indexing-protocol/the-advantages-of-account-centric-indexing.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.