> For the complete documentation index, see [llms.txt](https://purple-pay.gitbook.io/purple-pay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://purple-pay.gitbook.io/purple-pay/welcome-to-purple-pay.md).
# Welcome to Purple Pay
Regulatory-compliant, privacy-enabled, payment protocol to power payments seamlessly.
## Overview
The entire web3 ecosystem is infamous for non-compliance to regulations, and rightfully so. It is incredibly hard to identify someone on-chain and is in fact against the pseudonymity principles of web3 allowing for bad actors to flourish. However, for web3’s next stage of growth it requires to win the trust of regulation. Only then can institutional money and large scale retail capital to be allocated to projects that solve real problems and deliver value to consumers beyond speculation in a compliant manner.
The trillion dollar web3 industry has in the past decade of its existence proved product market fit. It has validated the hypothesis that people can permissionlessly transact and create value for each other in a decentralized manner. Upto 20% of entire populations of most countries now own cryptocurrency assets. All traditional finance asset classes have found an on-chain representation.
Most of the current levels of adoption, however, have stemmed from price speculation and not from technology adoption. Despite benefits of trust, autonomy, ownership, and composability, mass adoption still is a distant dream for the industry.
At Purple Pay, we're taking this challenge head-on and building the compliant financial lego blocks for web3 rails.
## Quick links
{% content-ref url="/pages/0lLJGNepsOzMmQmU2NTx" %}
[Quick start guide](/purple-pay/product-guides/quick-start-guide.md)
{% endcontent-ref %}
{% content-ref url="/pages/rnCBva5KbdfRjqaOmofX" %}
[Generate API Key](/purple-pay/developers/api-key/generate-api-key.md)
{% endcontent-ref %}
---
# 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://purple-pay.gitbook.io/purple-pay/welcome-to-purple-pay.md?ask=&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.