> For the complete documentation index, see [llms.txt](https://docs.apacx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apacx.io/xafer-waas/xafer-waas/introduction.md).
# Introduction
Xafer WaaS is an enterprise-grade Wallet-as-a-Service (WaaS) solution by APACX. Built on a robust MPC security architecture, Xafer is designed for financial platforms, Web3 projects, and SaaS providers—delivering secure, compliant wallet custody and signing infrastructure with minimal development effort.
### What is Xafer WaaS
\
Xafer WaaS is a modular wallet service platform that enables businesses to rapidly create and manage multi-chain wallets for their users, with customizable access controls, risk rules, and audit features. It supports both custodial and semi-custodial modes across major blockchains, allowing teams to focus on product growth without worrying about wallet infrastructure.
### What problems Xafer WaaS solve?
\
In traditional wallet systems—especially those self-built by enterprises—teams often struggle with key management risks, permission control, compliance complexity, and technical overhead. For many Web3 applications, building a secure and scalable wallet infrastructure becomes a major blocker to launching or expanding business.
Xafer WaaS solves these challenges head-on. Our MPC architecture eliminates single points of failure and prevents key exposure, while our flexible permission and approval systems support enterprise-level control and auditability. Xafer’s plug-and-play integration model further helps teams launch faster and stay focused on core product innovation—not backend infrastructure.
Whether you’re building a game, fintech platform, SaaS product, or operating across regulated markets, Xafer helps reduce your security burden, accelerate your go-to-market, and stay compliant with ease.
---
# 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.apacx.io/xafer-waas/xafer-waas/introduction.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.