diff --git a/docs/explanations/dapi.md b/docs/explanations/dapi.md
index 37ab2e0ff..c53f05a59 100644
--- a/docs/explanations/dapi.md
+++ b/docs/explanations/dapi.md
@@ -24,6 +24,11 @@ To overcome these obstacles, the Dash decentralized API (DAPI) uses Dash's robus
 
 DAPI protects connections by using TLS to encrypt communication between clients and the masternodes. This encryption safeguards transmitted data from unauthorized access, interception, or tampering. [Platform gRPC endpoints](../reference/dapi-endpoints-platform-endpoints.md) provide an additional level of security by optionally returning cryptographic proofs. Successful proof verification guarantees that the server responded without modifying the requested data.
 
+:::{note}
+See the [Query Capabilities page](./query.md) for more detailed information regarding Platform data
+retrieval.
+:::
+
 ## Endpoint Overview
 
 DAPI currently provides 2 types of endpoints: [JSON-RPC](https://www.jsonrpc.org/) and [gRPC](https://grpc.io/docs/guides/). The JSON-RPC endpoints expose some layer 1 information while the gRPC endpoints support layer 2 as well as streaming of events related to blocks and transactions/transitions. For a list of all endpoints and usage details, please see the [DAPI endpoint reference section](../reference/dapi-endpoints.md).
diff --git a/docs/explanations/query.md b/docs/explanations/query.md
new file mode 100644
index 000000000..a8a5624aa
--- /dev/null
+++ b/docs/explanations/query.md
@@ -0,0 +1,63 @@
+```{eval-rst}
+.. _explanations-query:
+```
+
+# Query Capabilities
+
+Dash Platform allows applications to retrieve data in a structured and deterministic manner. Clients
+query the latest committed state of identities, data contracts, documents, and other Platform data
+similar to traditional databases while retaining decentralized trust benefits.
+
+## Querying the State
+
+Queries operate on the finalized data stored within Platform’s state tree. Responses reflect the
+most recently committed block and do not include pending or historical intermediate changes.
+
+This means:
+
+- Query results are consistent across nodes
+- Clients do not need to process blockchain history
+- Data retrieval is deterministic and efficient
+
+:::{note}
+Queries return the *current finalized state*, not the sequence of events that created it.
+:::
+
+## Deterministic Results
+
+All queries produce deterministic results. The same query executed on two honest and up-to-date
+Platform nodes will always produce the same result. This ensures consistent application behavior
+regardless of which node provides the response.
+
+## Data Proofs
+
+Queries can return locally verifiable cryptographic proofs, allowing clients to verify response
+accuracy without trusting the responding node.
+
+Two types of proofs exist:
+
+| Proof Type | Purpose |
+|------------|---------|
+| Inclusion Proof | Confirms that specific data exists and has not been modified |
+| Non-Inclusion Proof | Confirms that specific data does *not* exist (useful for uniqueness checks such as usernames) |
+
+Proofs are especially valuable for:
+
+- Light clients
+- Browser-based and serverless environments
+- Trust-minimized applications
+
+## Indexed Queries
+
+Dash Platform requires queries to use indexes defined in the data contract for the relevant document
+type. If a field is not indexed, it cannot be used for filtering or sorting.
+
+Benefits of indexed querying include:
+
+- Predictable performance
+- Consistent execution across nodes
+
+:::{important}
+Indexes should be planned during contract design since there are [limited index update
+options](./platform-protocol-data-contract.md#contract-updates) for already registered contracts.
+:::
diff --git a/docs/index.md b/docs/index.md
index 2095793ff..92cf82361 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -137,6 +137,7 @@ explanations/dashpay
 explanations/fees
 explanations/tokens
 explanations/nft
+explanations/query
 ```
 
 ```{toctree}