> 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/example-hemera-use-cases/user-defined-ai-agents.md).

# User-defined AI Agents

{% hint style="warning" %}
Note: This is a roadmap item that is not yet available but under active development.
{% endhint %}

As a public goods protocol, Hemera's true strength lies in standardizing data access and Web3 LLM capabilities and providing them to empower the web3 ecosystem. Here user-defined AI agents here allows anyone to configure and fine tune agents according to their own domain knowledge, which can be insights on personal MEME coin trading strategy, or heuristics on identifying new smart money addresses, or personal favorite NFT assets. Once configured, the user-defined AI agents are attributed to their creators, and when used, creators can earn a percentage of the token spent. &#x20;


---

# 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/example-hemera-use-cases/user-defined-ai-agents.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.
