# Page Not Found

The URL `files/NYtzJDUiaqTsm96XMkV9` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [3.2 SMARTS](https://difacquim.gitbook.io/quimioinformatica/3.-representacion-molecular/3.2-smarts.md)
- [7.4 Panorama y acantilados de actividad](https://difacquim.gitbook.io/quimioinformatica/7.-similitud-quimica/7.4-panorama-y-acantilados-de-actividad.md)
- [3.1 SMILES](https://difacquim.gitbook.io/quimioinformatica/3.-representacion-molecular/3.1-smiles.md)
- [8.1 Reacciones químicas](https://difacquim.gitbook.io/quimioinformatica/8.-enumeracion-de-bibliotecas-quimicas/8.1-reacciones-quimicas.md)
- [8. Enumeración de bibliotecas químicas](https://difacquim.gitbook.io/quimioinformatica/8.-enumeracion-de-bibliotecas-quimicas.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://difacquim.gitbook.io/quimioinformatica/3.-representacion-molecular/3.2-smarts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://difacquim.gitbook.io/quimioinformatica/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://difacquim.gitbook.io/quimioinformatica/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/quimioinformatica/3.-representacion-molecular/3.2-smarts.md`).

You may also use `Accept: text/markdown` header for content negotiation.