# Documentation for LLMs

Use a compact index, complete documentation or individual Markdown pages in your coding assistant.

Canonical: https://docs.cyberrxn.com/en/docs/ai/llms

The documentation is available as ordinary HTML and clean Markdown. These resources help an assistant explain integration steps and work with the public API contract. Live reaction evidence comes from the connected chemistry service.

## Choose a format

| Resource | Use it when |
| --- | --- |
| [llms.txt](/llms.txt) | The assistant should discover relevant documentation before fetching selected pages |
| [llms-full.txt](/llms-full.txt) | Your client needs all documentation in one text resource and has room for the complete content |
| Individual page Markdown | You already know the guide or reference page needed for the task |
| [OpenAPI JSON](/openapi.json) | You need operation names, authentication, request fields or response schemas |
| [Current chemistry guide](https://mcp.cyberrxn.com/skills/reaction-evidence.md) | An agent needs instructions for chemistry evidence and action discovery |

Start with the index and fetch only relevant pages when context is limited. English and Russian documentation have their own URLs; retain the requested language when following links.

## Read a page as Markdown

Open a page and select **Open → View as Markdown**, or use **Copy Markdown**. For example:

```text
https://docs.cyberrxn.com/en/docs/quickstart.md
https://docs.cyberrxn.com/en/docs/sdk/python.md
https://docs.cyberrxn.com/en/docs/api/reference/validate-reaction.md
```

Clients that support content negotiation can request Markdown from the normal documentation URL:

```bash
curl -H 'Accept: text/markdown' \
  https://docs.cyberrxn.com/en/docs/quickstart
```

No API key is required to read public documentation. Confirm that the response is Markdown before processing it; a missing page remains a missing page.

## Give your assistant a specific task

> Read https://docs.cyberrxn.com/en/docs/quickstart.md and the Python SDK guide. Explain how to install the current downloadable SDK, load a key from the environment and validate a supplied reaction. Keep credentials out of source files.

Ask for the current installation guide: SDK archives are published with checksums, while registry availability is a separate release decision. Do not substitute a guessed package-manager command.

## Keep documentation and execution distinct

Reading documentation does not grant workspace access. To run a query, use an authenticated [MCP connection](/en/docs/mcp), [API key](/en/docs/api/keys) or supported SDK. To claim a recorded precedent, retrieve the full observation and inspect its source.

Static documentation can explain the workflow; the current `get_reaction_skill` response supplies live action discovery. See [skills](/en/docs/ai/skills) and [MCP tools](/en/docs/ai/tools) for an agent integration.