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

# Platform Architecture

The KryptoPips platform consists of the following main components.

**Web3 Wallet Connection:** A connection is established with the user’s cryptocurrency wallet, allowing them to approve blockchain transactions and execute actions on the platform.

**Integrated User Widget:** An embeddable app that can be integrated into any user-facing web module to allow users to carry out actions and interact with KryptoPips platform functionalities.

**Administrator Dashboard:** An admin panel that allows administrators to securely login to access user data and statistics for the purposes of monitoring and carrying out their operations.

<figure><img src="https://2429038874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnZV5625by9KRD8Ru8vDf%2Fuploads%2FItfR0bvxyrggEeeImWyQ%2FKTP%20System%20Diagram%20Dark.png?alt=media&amp;token=e52b5b70-3e22-4045-8c26-3e5329336e9c" alt=""><figcaption><p>KryptoPips Platform</p></figcaption></figure>


---

# 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://kryptopips.gitbook.io/whitepaper/platform/platform-architecture.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.