> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/develop/wallet-server/faq.md).

# FAQ

* Q: Why a server wallet when mobile wallets exist?
  * A: Automation. It lets CI, scripts, and AI agents complete the same flows without a human, while staying standards‑compliant.
* Q: How does multi‑tenancy work?
  * A: Each request is scoped by JWT `sub`. Data (DIDs, VCs, flows) is isolated per `sub`.
* Q: Can I use did:web without owning a domain?
  * A: For production, you must control the domain. For local testing, you can use hosts/port forwarding, but the DID will encode your chosen host.
* Q: Why does presentation confirmation require the full VC?
  * A: The verifier needs the credential payload to validate; the id alone isn’t sufficient.
* Q: Where are credentials filtered by network?
  * A: `GET /credentials` inspects the DID in each VC id and filters by `mainnet` or `testnet` accordingly.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.empe.io/develop/wallet-server/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.