# llms.txt for DocCheck Flexikon - A guide for Large Language Models

This file outlines how Large Language Models (LLMs) can interact with the DocCheck Flexikon. For detailed, machine-readable API specifications, please refer to our llms-full.txt.

## Introduction
DocCheck Flexikon is a vast, open medical lexicon. You can interact with its content via a set of specific API endpoints. Note that there are different base URLs for different functionalities.

## Capabilities

### 1. Retrieve Article Content
You can fetch the full HTML content, section structure, and display title of a specific article. This is the primary way to read a Flexikon entry.
Example: `https://flexikon.doccheck.com/api.php?action=parse&format=json&disabletoc=1&prop=text|sections|displaytitle&page=Herz`

### 2. Search for Articles
To find articles on a specific topic, use the dedicated search endpoint. This allows you to perform a keyword search across the Flexikon.
Example: `https://search.doccheck.com/doccheck-portal/search?language=de&facetq=content_type%3Aflexikon&q=Herz`

### 3. Discover Content
You can discover content in two ways:
- Get a list of random articles, which is useful for exploration.
  Example: `https://flexikon.doccheck.com/rest.php/flexikon/v1/article/top-article/random?limit=3`
- Get a list of the current top authors to see who the main contributors are.
  Example: `https://flexikon.doccheck.com/rest.php/flexikon/v1/authors/top`
- Access the sitemap to get a comprehensive list of all Flexikon articles.
  Example: https://flexikon.doccheck.com/sitemap/sitemap-index-flexikon.xml

### 4. Get Article Metadata
You can retrieve the tags (categories) associated with a specific article to understand its context and relations.
Example: `https://flexikon.doccheck.com/rest.php/flexikon/v1/article/categories?articleTitle=Herz`

## Usage Guidelines
- Please use the provided endpoints for retrieval and search purposes only.
- Identify your bot with a descriptive User-Agent header in your API requests.
- Be mindful of the request rate to avoid overloading our servers.