> For the complete documentation index, see [llms.txt](https://docs.nesa.ai/nesa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nesa.ai/nesa/using-nesa/getting-started/testnet-nesa-faucet.md).

# Testnet Nesa Faucet

The Nesa Testnet Faucet allows you to obtain test tokens, enabling you to explore and interact with the Nesa network without using real tokens. Testnet tokens are only for experimental purposes and have no real-world value.

{% hint style="info" %}
**Official Nesa Testnet Faucet:** [**https://beta.nesa.ai/faucet**](https://beta.nesa.ai/faucet)
{% endhint %}

***

### Distribution Amounts & Limits

As of the time of this writing, the faucet distributes NES as follows:

```
0.005 NES (5K unes): Nesa Account Holder
0.010 NES (10K unes): Nesa Account Holder, with X/Twitter Linked
```

In order to manage network utilization and fair use, the following request limits are in place:

```
Max 1 successful request per 24 hours per Nesa Account
60 seconds between requests per Nesa Account
```

***

### Via Nesa Web

You may use Nesa Web to request faucet tokens. This option is noteworthy for those who would like a rich interface with the option to quickly link their X/Twitter Account.

<figure><img src="/files/GKlMkPVfa3FeO5gnE9I4" alt="" width="375"><figcaption></figcaption></figure>

1. **Visit the Testnet Nesa Faucet Page (URL above)**
2. **(Optional) Authenticate your X/Twitter Account to Receive 2X Tokens**
3. **Connect Your Wallet**
4. **Request Tokens**

Upon requesting tokens, Nesa Web will respond with a message indicating the result of your request.

{% hint style="info" %}
**Note:** Connecting your wallet automatically populates the "wallet address" input field in order to mitigate typographical errors.
{% endhint %}

***

### Via Nesa Discord

Nesa provides an alternate route for requesting Testnet NES Tokens within the [**Nesa Discord**](https://discord.gg/nesa). Visit the Testnet Faucet channel and request tokens using the `/claim` command.

```markup
/claim [nesa_wallet_address: string]
```

Following your request, the Nesa faucet bot will respond with the status of your request.

{% hint style="info" %}
**Note:** You must have an active Nesa Account linked to the Discord account that is making the request.
{% endhint %}

***

### Via Telegram

Coming soon.

***

### Troubleshooting

If you encounter issues:

1. **Retry Your Request**:
   * Wait a few minutes and try your request again, taking note of any error messages returned from your request.
2. **Seek Assistance**:
   * Join the [**Nesa Discord**](https://discord.gg/nesa) for help.

***

By following these steps, you'll have the test tokens you need to explore and interact with Nesa Chain. Enjoy experimenting on the testnet!


---

# 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.nesa.ai/nesa/using-nesa/getting-started/testnet-nesa-faucet.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.
