# Page Not Found

The URL `getting-started/who-are-patchworks` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [What is Patchworks?](https://doc.wearepatchworks.com/product-documentation/welcome/what-is-patchworks.md)
- [Getting started introduction](https://doc.wearepatchworks.com/product-documentation/getting-started/getting-started-introduction.md)
- [Patchworks IPs](https://doc.wearepatchworks.com/product-documentation/getting-started/technical-overview/patchworks-ips.md)
- [Patchworks quickstart guide](https://doc.wearepatchworks.com/product-documentation/getting-started/patchworks-quickstart-guide.md)
- [Key concepts & terminology](https://doc.wearepatchworks.com/product-documentation/getting-started/key-concepts-and-terminology.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://doc.wearepatchworks.com/product-documentation/welcome/what-is-patchworks.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://doc.wearepatchworks.com/product-documentation/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://doc.wearepatchworks.com/product-documentation/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., `/product-documentation/welcome/what-is-patchworks.md`).

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