# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Comprehensive list of academic and technical references supporting the research](https://neurablock.gitbook.io/whitepaper/references/comprehensive-list-of-academic-and-technical-references-supporting-the-research.md)
- [Architecture components](https://neurablock.gitbook.io/whitepaper/system-architecture/architecture-components.md)
- [Criteria and Metrics for Evaluating Opcode Maliciousness](https://neurablock.gitbook.io/whitepaper/protection-oracle/criteria-and-metrics-for-evaluating-opcode-maliciousness.md)
- [Pioneering Cybersecurity Tools Powered by AI for Web 3.0](https://neurablock.gitbook.io/whitepaper/tools/pioneering-cybersecurity-tools-powered-by-ai-for-web-3.0.md)
- [Webapp protection/monitoring](https://neurablock.gitbook.io/whitepaper/protection-oracle/webapp-protection-monitoring.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://neurablock.gitbook.io/whitepaper/references/comprehensive-list-of-academic-and-technical-references-supporting-the-research.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://neurablock.gitbook.io/whitepaper/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://neurablock.gitbook.io/whitepaper/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., `/whitepaper/references/comprehensive-list-of-academic-and-technical-references-supporting-the-research.md`).

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