> 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/pl/tworzenie/podstawy/tokeny-testnet/tokeny-testnet-tatum-faucet.md).
# Tokeny testnet przez Tatum Faucet
Odbierz 10 bezpłatnych testowych tokenów CHZ co 24 godziny na Spicy Testnet z Faucet Tatum po zarejestrowaniu konta na Tatum Dashboard.
Spicy Faucet Tatum pozwala otrzymać 10 testowych tokenów CHZ co 24 godziny.
{% hint style="info" %}
Najpierw musisz zarejestrować się na [**Tatum Dashboard**](https://dashboard.tatum.io/signup).
{% endhint %}
Aby przetransferować testowe tokeny CHZ do swojego portfela za pomocą Faucet Tatum, wykonaj następujące kroki:
1. Przejdź do portfela MetaMask i skopiuj adres portfela do schowka.\_\
.png?alt=media)
2. Połącz się z [Tatum Dashboard](https://dashboard.tatum.io/).
3. Kliknij pozycję menu "Faucets" (może być konieczne przewinięcie w dół) lub [przejdź bezpośrednio na stronę](https://dashboard.tatum.io/faucets).
4. Przewiń do "Chiliz Spicy Testnet" (lub użyj paska wyszukiwania) i kliknij, aby otworzyć zakładkę.
5. Wklej adres portfela MetaMask w polu tekstowym.
6. Kliknij "Claim tokens".
W ciągu kilku minut powinieneś zobaczyć testowe tokeny CHZ w swoim portfelu.
---
# 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/pl/tworzenie/podstawy/tokeny-testnet/tokeny-testnet-tatum-faucet.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.
.png?alt=media)