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

# PillarX Docs

PillarX is an integrated Web3 experience aimed at users who want to explore the Web3 space in a trusted and easy to use environment.

We're thrilled you've decided to take a look at what's needed to develop your experience within PillarX. PillarX.

Your PillarX experience is easy to build and consists of just three base components:

* A `manifest.json`: this tells us some base information about your experience
* An PNG file called `icon.png`: to represent your app visually across PillarX
* An `index.tsx` entry file: a React component representing the start of your PillarX experience

Check out the Core Concepts below to read more about the PillarX platform, or jump straight to [Getting Started](https://docs.pillarx.app/start/getting-started.md).


---

# 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.pillarx.app/pillarx-docs.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.
