> For the complete documentation index, see [llms.txt](https://cagacrypto.gitbook.io/caga-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cagacrypto.gitbook.io/caga-whitepaper/ecosystem-development/testnet/faqs.md).

# FAQs

#### What is CAGA?

CAGA is a high-performance, EVM-compatible blockchain designed for rapid and cost-effective transactions. It provides developers and users with a robust platform for building and using decentralized applications (dApps).

#### What tokens are available on the testnet?

On the CAGA testnet, you can access CAGA tokens for general transactions, CNT for minting NFTs, and CTT for testing token swaps.

#### How often can I get CAGA from the faucet?

The faucet allows you to claim 1 CAGA token per address every 24 hours. This limitation ensures fair access for all users to test the network.

#### What is CNT?

CNT, or CAGA Network Token, is specifically used within the testnet environment for minting non-fungible tokens (NFTs), allowing you to simulate the creation and management of NFTs.

#### What is CTT?

CTT, or CAGA Test Token, is utilized for simulating swaps on the CAGA DEX. It helps developers test swap functionalities and other related features within the DEX environment.


---

# 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://cagacrypto.gitbook.io/caga-whitepaper/ecosystem-development/testnet/faqs.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.