# US-043 — Dashboard model search and model cards

Status: planned
Priority: Medium (post-deploy polish)
Stage: Idea

## Context

The dashboard shows nodes/routes/billing but nothing model-centric. Operators
and testers should be able to search for a model and see, per model, a card
with what the network knows about it.

## Scope

- **Search**: query box hitting a new tracker endpoint that proxies the HF Hub
  search API (server-side, so the dashboard stays CSP-clean and unauthenticated
  browsers aren't rate-limited) merged with the tracker's own model presets and
  currently-served models.
- **Model card** per result:
  - name, architecture, params, layer count (reuse `model_metadata_for`,
    which now handles nested `text_config` — US layer-detection fix)
  - coverage on the network: which layer ranges are served, by how many nodes,
    coverage gaps (the Coverage Map already exists on the tracker)
  - price per 1K tokens, availability (routable now? single-hop or pipeline?)
  - memory footprint per quantization where known (bf16 / GGUF sizes)
  - action: "request this model" — flags demand so node operators (or
    auto-shard assignment) know what to load next
- Featured models section driven by the curated catalog (`CURATED_MODELS`),
  including GGUF entries once US-042 lands.

## Acceptance criteria

- Searching a HF repo id or free text returns results without the browser
  calling HF directly
- A served model's card shows live coverage and a working "chat now" state
- An unserved model's card shows the "request" action and estimated memory
  per quant
- `python -m pytest` passes from repo root
