> For the complete documentation index, see [llms.txt](https://wiki.whop.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.whop.com/readme.md).
# Whop Wiki
Internal documentation powered by Mintlify.
## Prerequisites
* Node.js 20+ (configured in `mise.toml`)
## Quick Start
```bash
cd docs
npx mintlify dev
```
The documentation will be available at `http://localhost:3000`.
## Building for Production
```bash
npx mintlify build
```
## Folder Structure
```
docs/
├── docs.json # Mintlify configuration
├── mise.toml # Node version management
├── brand-assets/ # Logos, fonts, illustrations
├── home/index.mdx # Home page
├── company/ # Company section
├── engineering/ # Engineering section
├── payments/ # Payments section (with subsections)
├── core-product/ # Core Product section
├── finance/ # Finance section
├── dashboard/ # Dashboard section
├── affiliates/ # Affiliates section
└── ads/ # Ads section
```
## Adding Custom Fonts
The brand assets include Acid Grotesk fonts in `.otf` format. Mintlify requires `.woff2` format.
1. Convert `.otf` to `.woff2` using [CloudConvert](https://cloudconvert.com/otf-to-woff2)
2. Add to a `fonts/` directory
3. Update `docs.json`:
```json
{
"fonts": {
"heading": {
"family": "Acid Grotesk",
"source": "/fonts/AcidGrotesk-Bold.woff2",
"format": "woff2",
"weight": 700
},
"body": {
"family": "Acid Grotesk",
"source": "/fonts/AcidGrotesk-Regular.woff2",
"format": "woff2",
"weight": 400
}
}
}
```
## Components
**Callouts:**
```mdx
Info message
Warning message
Note message
```
**Cards:**
```mdx
Description
```
**Tabs:**
```mdx
Content
Content
```
## Deployment
Connect your GitHub repository at [mintlify.com](https://mintlify.com) for automatic deployments.
## Resources
* [Mintlify Docs](https://mintlify.com/docs)
---
# 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://wiki.whop.com/readme.md?ask=&goal=
```
`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.