# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [7.1 Serving models through an API](https://4bcplaybook.clearglobal.org/7-development-and-deployment-guidelines/7.1-serving-models-through-an-api.md)
- [3.1 Enabling Organizations with Language Technology](https://4bcplaybook.clearglobal.org/3.-partner-opportunities/3.1-enabling-organizations-with-language-technology.md)
- [4.1 Setting criteria to help choose the use case](https://4bcplaybook.clearglobal.org/4.-identifying-impactful-use-cases/4.1-setting-criteria-to-help-choose-the-use-case.md)
- [3.2 Bridging the Technical Gap](https://4bcplaybook.clearglobal.org/3.-partner-opportunities/3.2-bridging-the-technical-gap.md)
- [3.3 Dealing with language technology providers](https://4bcplaybook.clearglobal.org/3.-partner-opportunities/3.3-dealing-with-language-technology-providers.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://4bcplaybook.clearglobal.org/7-development-and-deployment-guidelines/7.1-serving-models-through-an-api.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://4bcplaybook.clearglobal.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://4bcplaybook.clearglobal.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., `/7-development-and-deployment-guidelines/7.1-serving-models-through-an-api.md`).

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