# Public Pages

These QuickPod console pages can be opened directly without logging in and are suitable for public documentation, sharing, and external linking.

## Search and discovery

* [GPU Search](https://console.quickpod.io/)
* [CPU Search](https://console.quickpod.io/cpu-pod-search)
* [Templates](https://console.quickpod.io/templates)
* [GPU Catalog](https://console.quickpod.io/gpu-types)

## Marketplace and host discovery

* [Host Stores Directory](https://console.quickpod.io/host-stores)
* Host storefront pattern: `https://console.quickpod.io/store/<slug>`

## Product landing pages inside the console

These routes currently act as public product surfaces when a visitor is not authenticated:

* [Clusters](https://console.quickpod.io/clusters)
* [Serverless](https://console.quickpod.io/serverless)
* [Storage](https://console.quickpod.io/storage)
* [System Status](https://console.quickpod.io/system-status)
* [Refer & Earn](https://console.quickpod.io/refer)

## Authentication pages

* [Log In](https://console.quickpod.io/log-in)
* [Sign Up](https://console.quickpod.io/sign-up)

## How to use these links in docs

Use direct public links in documentation when:

* the page is useful before login
* you are documenting public discovery or marketplace browsing
* you want users to jump directly into the correct console surface

Avoid linking authenticated internal routes as public documentation links unless the page is specifically being described as login-required.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.quickpod.io/console/public-pages.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.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.