# Generate llms.txt and llms-full.txt for a docs site

**Use case:** 

Crawl a documentation site and get ready-to-host llms.txt and llms-full.txt files, plus each page as Markdown. It stays under the path you give it and follows robots.txt.

## Input

```json
{
  "startUrl": "https://www.python-httpx.org/",
  "maxPages": 20,
  "siteTitle": "HTTPX",
  "concurrency": 5
}
```

## Output

```json
{
  "url": {
    "label": "URL",
    "format": "string"
  },
  "title": {
    "label": "Title",
    "format": "string"
  },
  "wordCount": {
    "label": "Words",
    "format": "integer"
  },
  "likelyClientRendered": {
    "label": "Likely JS-only",
    "format": "boolean"
  },
  "markdown": {
    "label": "Markdown",
    "format": "string"
  },
  "headings": {
    "label": "Headings",
    "format": "array"
  }
}
```

## How it works

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

The Docs to Markdown and llms.txt Actor is ready to run with the inputs already set for "Generate llms.txt and llms-full.txt for a docs site". [Sign up or log in](https://console.apify.com/create-task-from-example/6A2J5zFN8YBGw6sqS) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Generate llms.txt and llms-full.txt for a docs site" task

The Docs to Markdown and llms.txt Actor will start running based on the input automatically. You can also change all the input fields, like docs url, max pages, and more, to match your specific use case.

### 3. Receive the "Generate llms.txt and llms-full.txt for a docs site" 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, words, 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 "Generate llms.txt and llms-full.txt for a docs site" task via API](https://apify.com/metaparse/docs-to-markdown.md).

## FAQ

### Where are the files?

In the run's key-value store, as llms.txt and llms-full.txt. The Output tab links to both.

## About this Actor

This example demonstrates how to use [Docs to Markdown and llms.txt](https://apify.com/metaparse/docs-to-markdown.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/metaparse/docs-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/metaparse/docs-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`).