# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Technical Implementation Path](https://docs.mercurynet.org/2.-technical-architecture/technical-implementation-path.md)
- [Phase 4: Business Clients Paid Verification Model (25-36 Months)](https://docs.mercurynet.org/3.-phased-business-model/phase-2-business-clients-paid-verification-model-13-24-months.md)
- [Phase 2: Individual Users Payment Model (7-12 Months)](https://docs.mercurynet.org/3.-phased-business-model/phase-2-individual-users-payment-model-7-12-months.md)
- [Phase 3: Individual Users Payment Model ( 13-24Months)](https://docs.mercurynet.org/3.-phased-business-model/phase-1-individual-users-payment-model-0-12-months.md)
- [Phase 5: Solutions for Government Clients(37-48 Months)](https://docs.mercurynet.org/3.-phased-business-model/phase-3-solutions-for-government-clients-25-48-months.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://docs.mercurynet.org/2.-technical-architecture/technical-implementation-path.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://docs.mercurynet.org/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.mercurynet.org/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., `/2.-technical-architecture/technical-implementation-path.md`).

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