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

# MoonClick

A Brief Message From Our Team <3

## Our Mission

At Moonclick, we believe systems should be built to serve the average user fairly, and that true fairness naturally exposes corruption. Moonclick embodies this philosophy through trust-centric yet trust-independent systems.

Looking at the current state of our industry, it's clear that trust has become a scarce commodity. Moonclick aims to decentralize and democratize coin creation on Solana, putting power back where it belongs: in the hands of users rather than gatekeepers.

Our approach recognizes a fundamental truth: the best systems are those that don't require you to trust them blindly, but instead earn trust through transparency and fair operation.


---

# 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.moonclick.io/moonclick.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.