# Architecture

QS framework foundation is made up of the following core components, which developers can leverage to create robust dApps:

#### 1. [**Session API**](#id-1.-session-api)

* Manages user sessions—**create**, **join**, and **terminate** sessions.
* Controls access via optional **passwords** or **address** **whitelists**, enabling fine-grained participation control.
* Issues roles like **Host** or **Client**, tracks session metadata such as session duration and user count.

#### 2. [**Upload API** ](#id-2.-upload-api)

* Provides **multipart uploads**, resumable transfer support, and metadata management.
* Facilitates secure uploads and downloads of encrypted content in a decentralized fashion, with file lifecycle managed per session context.

#### 3. [**Chats API**](#id-3.-chats-api)

* Enables real-time **messaging**, including sending and retrieving encrypted chat messages.
* Supports **reactions** (emoji or custom) and **pinning** of important messages for context and emphasis.

#### 4. [**Wallet Verification API (Web3 Integration)**](#id-4.-wallet-verification-api-web3-integration)

* Issues access tokens upon wallet verification which are required for accessing protected APIs, ensuring only verified identity holders access encrypted operations.

#### 5. [**Real-Time Events Engine**](#id-5.-real-time-events-engine)

* Use of **WebSockets** to deliver real-time events such as new messages, sessions updates, upload progress, etc.
* Use of **Webhooks** \[Coming soon]

{% content-ref url="/spaces/urDD06rcG5VUlokCaHZs/pages/EH5QeCoArvxwQKD0veFL" %}
[Introduction](/qs-framework/introduction.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.quicksync.me/framework/architecture-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.