> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/develop/basics/how-tos.md).

# How-Tos

Practical how-tos using Moralis, Tatum, thirdweb, and Nodit APIs on Chiliz Chain: wallet balances, transaction history, NFT metadata, and AI-assisted dApp building.

Chiliz Chain is fully compatible with Ethereum-centric frameworks and third-party tools.

This compatibility allows developers to use familiar Ethereum development processes and integrate advanced functionalities.

In this section, we give you some simple examples using EVM tools that integrate Chiliz Chain:

* [Moralis](https://moralis.com/): As an extensive framework for Web3 developers, Moralis provides several EVM-centric APIs, allowing you to deliver projects more quickly.\
  Read [Moralis' Chiliz-specific documentation](https://docs.moralis.com/web3-data-api/evm/chains/chiliz).
* [Tatum](https://tatum.io/): As a unified framework for building Web3 apps, Tatum provides several EVM-centric APIs, allowing you to deliver projects more quickly.\
  Read [Tatum's Chiliz-specific documentation](https://docs.tatum.io/reference/rpc-chiliz).
* [thirdweb](https://thirdweb.com/): thirdweb is a platform offering tools and infrastructure for building decentralized applications on multiple blockchain networks. It simplifies blockchain integration with SDKs, APIs, and pre-built components. Read [thirdweb's Chiliz page](https://thirdweb.com/chiliz-chain).
* [Nodit](https://nodit.io/): Nodit provides tools that make it easy to develop in a variety of multi-chain environments and reliable node services.\
  Read [Nodit's Chiliz-specific API reference](https://developer.nodit.io/en/api/chiliz/web3-data-api/getblockbyhashornumber/).

{% content-ref url="/pages/kVBVGzzFzE9a9XaoN4EU" %}
[How to get the balance of a wallet](/develop/basics/how-tos/how-to-get-the-balance-of-a-wallet.md)
{% endcontent-ref %}

{% content-ref url="/pages/OTBYMVSIMMrAMWQJcnap" %}
[How to get the history of a wallet](/develop/basics/how-tos/how-to-get-the-history-of-a-wallet.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZUCl1jCin6lhJPA2pX6W" %}
[How to get the metadata of a specific NFT](/develop/basics/how-tos/how-to-get-the-metadata-of-a-specific-nft.md)
{% endcontent-ref %}

We encourage you to explore all these platforms further, and see which one fits your development practices and preferences.

Besides blockchain frameworks, you can rely on vibe-coding tools to help you build your Chiliz Chain project:

{% content-ref url="/pages/PGfW4lG3ffqNvgzpf3fq" %}
[How to build a Chiliz dApp with AI tools](/develop/basics/how-tos/how-to-build-a-chiliz-dapp-with-ai-tools.md)
{% endcontent-ref %}


---

# 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.chiliz.com/develop/basics/how-tos.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.