> For the complete documentation index, see [llms.txt](https://docs.ternoa.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ternoa.network/getting-started/javascript-sdk/ternoa-indexer/dictionary/make-queries-on-the-dictionary.md).

# Make queries on the dictionary

### **Use the dictionary as an explorer**

*The main interest of the dictionary is to have a middleman database between the blockchain and the indexer. Again, this database will allow the indexer to query block metadata directly from the dictionary. This means that if we want to get only NFT creation events, the indexer will ask the dictionary for the corresponding blocks. (So, for example, instead of fetching blocks 0 to 100, it will fetch only the numbers 5, 16, and 94 because that’s where NFTs are created.)*

Another use of the dictionary is to record all generic data that can be used for an explorer. For example, block, transaction (extrinsic), and event data. This data is then used to display chain information. (See the [**ternoa scan**](https://explorer.ternoa.com/)) You can also compare the basic dictionary template provided by the Subquery team and the dictionary used by Ternoa which also records data for its explorer.

* [Subquery dictionary template](https://github.com/subquery/subql-dictionary)
* [Ternoa dictionary](https://github.com/capsule-corp-ternoa/ternoa-subql-dictionary)

[The dictionary playground](https://dictionary-mainnet.ternoa.dev/) will work the same as the Indexer. You will be able to perform queries the same as you do on the indexer, with the same syntax.


---

# 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.ternoa.network/getting-started/javascript-sdk/ternoa-indexer/dictionary/make-queries-on-the-dictionary.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.