# Turn documentation pages into Markdown for RAG

**Use case:** 

Convert documentation or help-center pages into clean Markdown, ready to chunk and embed in a vector database for retrieval-augmented generation. Code blocks are fenced and tables become GitHub-flavored Markdown. This example converts two Apify docs pages; paste in your own list of URLs.

## Input

```json
{
  "urls": [
    "https://docs.apify.com/actors",
    "https://docs.apify.com/storage/dataset"
  ],
  "mainContentOnly": true,
  "keepLinks": true,
  "keepImages": false,
  "concurrency": 10
}
```

## Output

```json
{
  "url": {
    "label": "Url"
  },
  "title": {
    "label": "Title"
  },
  "description": {
    "label": "Description"
  },
  "wordCount": {
    "label": "Word count"
  },
  "markdown": {
    "label": "Markdown"
  },
  "error": {
    "label": "Error"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Webpage to Markdown for LLMs & RAG (Clean, Bulk) Actor is ready to run with the inputs already set for "Turn documentation pages into Markdown for RAG". [Sign up or log in](https://console.apify.com/create-task-from-example/fVwAcg6bywO6g1dKh) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Turn documentation pages into Markdown for RAG" task

The Webpage to Markdown for LLMs & RAG (Clean, Bulk) Actor will start running based on the input automatically. You can also change all the input fields, like page urls, main content only, and more, to match your specific use case.

### 3. Receive the "Turn documentation pages into Markdown for RAG" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as url, title, description, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Turn documentation pages into Markdown for RAG" task via API](https://apify.com/quillbit-tools/webpage-to-markdown.md).

## About this Actor

This example demonstrates how to use [Webpage to Markdown for LLMs & RAG (Clean, Bulk)](https://apify.com/quillbit-tools/webpage-to-markdown.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/quillbit-tools/webpage-to-markdown.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/quillbit-tools/webpage-to-markdown.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).