# Host Stores & Analytics

Public host directory: <https://console.quickpod.io/host-stores>

Authenticated host routes:

* `/my-store`
* `/occupancy`
* `/contracts`
* `/earnings`

## Host stores

QuickPod now includes a host storefront model, not just raw marketplace listings.

Hosts can maintain a public-facing store profile with branding and a shareable store URL. Users can browse host-specific offers from the public host directory and then open a host's storefront directly.

## Public browsing flow

1. Open [Host Stores](https://console.quickpod.io/host-stores).
2. Choose a host storefront.
3. Browse the host's currently listed offers.
4. Launch from that storefront if the offer fits the workload.

## Occupancy analytics

The occupancy route gives hosts a dedicated view into utilization and marketplace activity. This is part of the newer host experience and should be treated as a first-class host operations page.

## Contracts

The contracts route helps hosts inspect contract and workload-related cost history tied to their listings.

## Earnings and payouts

The host earnings surface is broader than the older docs suggest. Hosts now manage payout setup and review payout-related history through the current console experience.

## Why this matters for docs

Older QuickPod docs described hosts mainly as machine listers. The current console also gives hosts public discovery, branding, analytics, and payout-management surfaces that deserve explicit documentation.


---

# 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/hosting/host-stores-and-analytics.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.
