Skip to main content
Access AI-optimized content and AI tool integrations via the Copy page dropdown on any WhiteBIT documentation page. The Copy page dropdown is available at the top of every documentation page. The menu provides options to copy page content for AI consumption, open pages directly in AI chat tools, and connect development environments to the full documentation via MCP.

Access the contextual menu

Select the Copy page dropdown next to the document title on any page. The menu opens with all available options grouped by function.

Page content options

Copy page

Copies the current page content as standard Markdown. Use when sharing documentation content or pasting into a text editor.

Copy page as Markdown for LLMs

Copies the current page content in an AI-optimized Markdown format with additional context for language models. Use when feeding page content to an AI tool for analysis or asking questions about a specific page.

View as Markdown

Opens a plain-text Markdown view of the current page. Use when previewing the raw content of a documentation page.

Open in AI tool

Each option opens the current page content in the selected AI chat tool with the page pre-loaded as context.
OptionAI toolBest for
Open in ChatGPTChatGPT (OpenAI)Quick questions about the current page
Open in ClaudeClaude (Anthropic)Detailed analysis or code generation from the current page
Open in PerplexityPerplexityResearch-oriented questions about the current page
Open in GrokGrok (xAI)Questions and analysis with the current page as context

MCP and IDE quick connect

The contextual menu includes one-click options to connect a development environment to the WhiteBIT documentation MCP server at https://docs.whitebit.com/mcp.
OptionAction
Copy MCP Server URLCopies https://docs.whitebit.com/mcp to the clipboard for manual configuration
Connect to CursorOpens Cursor with the WhiteBIT MCP server pre-configured
Connect to VS CodeOpens VS Code with the WhiteBIT MCP server pre-configured
For manual configuration steps in Cursor, VS Code, and Claude Desktop, see the IDE and AI client setup guide.

Full documentation context

The following URLs provide the complete WhiteBIT documentation in AI-optimized formats for use with any AI tool that accepts pasted or linked content.
ResourceURLUse when
Documentation indexhttps://docs.whitebit.com/llms.txtDiscovering all available pages before exploring further
Full documentationhttps://docs.whitebit.com/llms-full.txtProviding comprehensive documentation context across the entire API reference

Common workflows

Ask questions about the current page

  1. Navigate to any WhiteBIT documentation page.
  2. Select the Copy page dropdown next to the document title.
  3. Select Open in ChatGPT, Open in Claude, Open in Perplexity, or Open in Grok.
  4. The AI tool opens with the page content pre-loaded. Ask questions about the current page.

Copy content for a local AI tool

  1. Navigate to any WhiteBIT documentation page.
  2. Select the Copy page dropdown next to the document title.
  3. Select Copy page as Markdown for LLMs.
  4. Paste the content into the preferred AI tool and ask questions.

Get comprehensive documentation context

  1. Navigate to https://docs.whitebit.com/llms-full.txt.
  2. Copy the URL or file content.
  3. Use when questions span multiple areas of the API documentation.

Connect an IDE to the documentation

  1. Navigate to any WhiteBIT documentation page.
  2. Select the Copy page dropdown next to the document title.
  3. Select Connect to Cursor or Connect to VS Code.
  4. For manual configuration or Claude Desktop setup, see IDE and AI client setup via MCP.

Best practices

Provide context Include relevant details when asking AI questions:
  • Mention the specific API endpoint or feature in scope.
  • Include code snippets when asking about implementation.
  • For questions that span multiple pages, use llms-full.txt for comprehensive context.
Combine approaches
  • Use the contextual menu for quick, page-specific questions and one-off tasks.
  • Use the IDE and AI client setup for ongoing development with full documentation search.
  • Both approaches work together for optimal AI assistance.

What’s next