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

# FAQ

1. **Do I need an API key to use the widget?**
   * No, widget partners use a **Partner ID** instead of an API key. This ID is assigned once the partnership is confirmed.
2. **Can we change our markup percentage later?**
   * Yes. Any change to your markup can be done upon request and will apply prospectively to all subsequent transactions after confirmation.
3. **Is there a minimum volume requirement?**
   * There’s no fixed minimum, but consistent traffic or embedded placement is recommended for reliable revenue performance.
4. **Can I customise the widget theme?**
   * No, As now there is fixed theme but we will work on this future if there is enough demand for it
5. **Who performs KYC/AML checks?**
   * All user identity verification and compliance checks are handled directly within the Vortex Widget via regulated partners.
6. **What happens if the service is down or under maintenance?**
   * You’ll be notified of planned maintenance periods in advance and also Vortex widget shows up a banner for the same
7. **How is attribution handled?**
   * Attribution is fully based on your **Partner ID**. Any transaction initiated from your link or embedded widget is tracked automatically under your partner profile.


---

# 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.vortexfinance.co/hosted-app/faq.md?ask=<question>&goal=<user_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.